release: 0.12.1#393
Open
stainless-app[bot] wants to merge 5 commits into
Open
Conversation
843110e to
9925a2e
Compare
9925a2e to
d16eff0
Compare
d16eff0 to
fc30981
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-05)
Full Changelog: v0.12.0...v0.12.1
Bug Fixes
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 automated patch release removes the now-unnecessary
agent_idandtask_idparameters from thestates.update()method (both sync and async), and improves docstrings across task-creation param types to clarify the get-or-create semantics of thenamefield.states.update()signature fix:agent_idandtask_idare removed from method signatures,StateUpdateParams, and the PUT request body;state_idin the URL path is the only identifier needed.nameandparamsinParamsCreateTaskRequest(across three RPC param files and the ADKacp.pymodule) now explicitly describe get-or-create behavior and warn that providing aparamsvalue on a name-collision overwrites the existing task's params.states.update()test call-sites are updated in lockstep with the signature change.Confidence Score: 5/5
Safe to merge — the change is a focused API cleanup that removes two parameters the server no longer expects, with consistent updates to the type definitions and tests.
All three layers (method signatures, TypedDict, and tests) are updated in sync. The doc-string changes are additive and accurate. No logic beyond parameter removal was touched.
No files require special attention.
Important Files Changed
agent_idandtask_idparameters from both sync and asyncupdate()method signatures and the request body transformation; method now only sendsstatein the body.agent_idandtask_idfromStateUpdateParamsTypedDict, leaving only thestaterequired field — aligned with the states.py method signature change.create_taskclarifying the get-or-create semantics of thenameparameter and the implications of omitting vs. providing a unique name.nameandparamsinParamsCreateTaskRequestto clarify get-or-create behavior.agent_rpc_params.pyfor the parallelParamsCreateTaskRequesttype.ParamsCreateTaskRequestin the deployment-preview RPC params type.agent_idandtask_idfrom all eightstates.update()test call-sites (both sync and async variants) to match the updated method signature.Sequence Diagram
sequenceDiagram participant Caller participant StatesResource participant API Note over Caller,API: Before (0.12.0) Caller->>StatesResource: update(state_id, agent_id, state, task_id) StatesResource->>API: "PUT /states/{state_id} body: {agent_id, state, task_id}" Note over Caller,API: After (0.12.1) Caller->>StatesResource: update(state_id, state) StatesResource->>API: "PUT /states/{state_id} body: {state}"Reviews (4): Last reviewed commit: "release: 0.12.1" | Re-trigger Greptile