chore: release main - #487
Open
stainless-app[bot] wants to merge 4 commits into
Open
Conversation
#485) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…r span (#484) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
August 6, 2026 21:33
8c9eeac to
2af8c8b
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.23.0
0.23.0 (2026-08-06)
Full Changelog: agentex-client-v0.22.2...agentex-client-v0.23.0
Features
agentex-sdk: 0.23.0
0.23.0 (2026-08-06)
Full Changelog: agentex-sdk-v0.22.2...agentex-sdk-v0.23.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
The PR prepares the 0.23.0 client and SDK release while adding business-span correlation and OpenTelemetry propagation across Temporal boundaries.
Confidence Score: 5/5
The PR appears safe to merge.
No blocking failure remains within the scope of this follow-up review.
Important Files Changed
Sequence Diagram
sequenceDiagram participant ACP as ACP handler participant Client as Temporal client participant Workflow as Temporal workflow participant Activity as Temporal activity participant Trace as Business tracing participant Obs as Observability backend ACP->>Client: Start workflow or send signal Client->>Workflow: Temporal request with OTel context Workflow->>Activity: Execute activity with propagated context Activity->>Trace: Start business span Trace->>Obs: Correlate business and OTel span IDs Activity->>Trace: End business span Trace->>Obs: Close span and record error statusReviews (2): Last reviewed commit: "chore: release main" | Re-trigger Greptile