release: 0.12.1#393
Open
stainless-app[bot] wants to merge 3 commits into
Open
Conversation
843110e to
9925a2e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.12.1 (2026-06-03)
Full Changelog: v0.12.0...v0.12.1
Documentation
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Greptile Summary
This is an automated patch release (0.12.1) that contains only documentation improvements — no logic, API, or behavioral changes. All version strings, the changelog, and the OpenAPI spec reference are updated consistently.
namefield): ThreeParamsCreateTaskRequestTypedDicts and theacp.pycreate_taskhelper now document the get-or-create-by-name semantics, the uniqueness requirement, and the recommendation to append a UUID when a fresh task is always desired.paramsfield): The same three TypedDicts now note that supplyingparamson a get-or-create hit overwrites the existing task's params rather than being a no-op.Confidence Score: 5/5
Safe to merge — exclusively documentation and version-bump changes with no runtime behavior affected.
Every changed line is either a version string, changelog entry, OpenAPI spec hash, or docstring. No executable code paths were modified.
No files require special attention.
Important Files Changed
create_taskname parameter expanded to explain get-or-create semantics and uniqueness requirement; no logic changes.nameandparamsfields inParamsCreateTaskRequestclarified to document get-or-create behavior and param-overwrite side-effect; no logic changes.agent_rpc_params.pyapplied to the by-name variant; no logic changes.ParamsCreateTaskRequest; no logic changes.__version__constant bumped from 0.12.0 to 0.12.1 to match pyproject.toml.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["task/create called"] --> B{name provided?} B -- No --> C["Always creates a fresh task"] B -- Yes --> D{name exists?} D -- No --> E["Creates a new task with that name"] D -- Yes --> F["Returns existing task\n(get-or-create)"] F --> G{params provided?} G -- Yes --> H["Overwrites existing task's params\n(not a pure read)"] G -- No --> I["Returns task as-is"]Reviews (2): Last reviewed commit: "release: 0.12.1" | Re-trigger Greptile