chore: release main#457
Open
stainless-app[bot] wants to merge 27 commits into
Open
Conversation
… delivery adapters, emitter) (#412)
…gModel (#355) Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com> Co-authored-by: Declan Brady <declan.brady@scale.com> Co-authored-by: Nitesh Dhanpal <NiteshDhanpal@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…quivalence [AGX1-373] (#414)
…est) (#438) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…5f2fe01d48613aaa6fcf--merge-conflict' into next
7f73c97 to
e6d57e8
Compare
e90258c to
942191a
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
add stable schedule handle endpoints
942191a to
536bd0a
Compare
536bd0a to
f72146b
Compare
f72146b to
a6e3f7f
Compare
a6e3f7f to
0b1126b
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.
✨ Stainless prepared a new release
agentex-client: 0.18.0
0.18.0 (2026-07-10)
Full Changelog: agentex-client-v0.17.0...agentex-client-v0.18.0
Features
Bug Fixes
Chores
agentex-sdk: 0.18.0
0.18.0 (2026-07-10)
Full Changelog: agentex-sdk-v0.17.0...agentex-sdk-v0.18.0
Bug Fixes
Chores
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 the 0.18.0 release for both
agentex-clientandagentex-sdk, generated by Stainless. It ships a significant refactor of the Schedules API and a dependency pin fix.schedule_name) to ID-based routing (schedule_id), with new "by-name" variants added for all operations (retrieve, update, pause, resume, trigger, delete).unpauseis replaced byresume, a newupdate(PATCH) method is added, andcreatedropstask_queue/workflow_name/workflow_paramsin favor of a structuredinitial_inputdict plustask_metadata/task_params/timezone.adk/pyproject.tomltightens the openai upper bound from<3to<2.45to work around a pydanticValidationErrorin openai-agents 0.14.x when openai 2.45+ makesInputTokensDetails.cache_write_tokensa required field.Confidence Score: 5/5
Safe to merge — all changes are auto-generated SDK code with a well-justified dependency pin fix.
The schedules resource is entirely generated by Stainless and correctly mirrors the updated OpenAPI spec. The openai upper-bound change is a targeted, clearly explained workaround for a known pydantic ValidationError in openai-agents 0.14.x. No hand-written logic was modified and all new types/methods are internally consistent.
No files require special attention. The path_name naming in update_by_name is a minor usability quirk from the code generator, not a correctness concern.
Important Files Changed
Reviews (6): Last reviewed commit: "chore: release main" | Re-trigger Greptile