chore: release main - #464
Open
stainless-app[bot] wants to merge 6 commits into
Open
Conversation
…t in workflow templates
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 21, 2026 18:29
7f14903 to
e70f46e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 21, 2026 23:06
e70f46e to
74d4c40
Compare
…ty trace (#465) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 24, 2026 06:19
74d4c40 to
2365a59
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 27, 2026 17:57
2365a59 to
91b6dde
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.21.0
0.21.0 (2026-07-27)
Full Changelog: agentex-client-v0.20.0...agentex-client-v0.21.0
Features
Bug Fixes
agentex-sdk: 0.21.0
0.21.0 (2026-07-27)
Full Changelog: agentex-sdk-v0.20.0...agentex-sdk-v0.21.0
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 automated Stainless release PR bumping both
agentex-clientandagentex-sdkfrom 0.20.0 to 0.21.0. The substantive changes are: OTel/ddtrace correlation tags (obs.trace_id,obs.span_id) are now injected into business spans via the newobs_ids.pymodule; theinclude_liveparameter is added to the schedules list method; andparamsis removed fromTaskListResponseItem(a security/correctness fix since it could expose per-caller secrets and PII in list responses).obs_ids.py: Reads the active OTel or ddtrace context (gated bySGP_OBS_MODE) and returns correlation tags that are merged into every business span'sserialized_data, enabling pivot from a business span to the per-turn observability trace.include_livefor schedules list: Both sync and asyncSchedulesResource.list()gain aninclude_live: boolquery parameter; all schedule response models also gainlive_data_available: Optional[bool].paramsremoved from task list response:TaskListResponseItem.paramsis dropped to prevent accidental exposure of create-time payloads containing secrets/PII; callers should useGET /tasks/{id}for the full record.Confidence Score: 5/5
Safe to merge — all changes are generated SDK code, a well-isolated new tracing helper, and an intentional removal of a field that was leaking PII.
The diff is almost entirely Stainless-generated code (version bumps, type additions, parameter additions). The one hand-written addition, obs_ids.py, is self-contained, fails gracefully when neither opentelemetry nor ddtrace is installed, never overwrites the run-level business trace_id, and merges safely into existing span data. The params removal is intentional and documented.
Files Needing Attention: No files require special attention.
Important Files Changed
Reviews (5): Last reviewed commit: "chore: release main" | Re-trigger Greptile