chore: release main#461
Open
stainless-app[bot] wants to merge 2 commits into
Open
Conversation
#460) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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.1
0.18.1 (2026-07-13)
Full Changelog: agentex-client-v0.18.0...agentex-client-v0.18.1
Bug Fixes
agentex-sdk: 0.18.1
0.18.1 (2026-07-13)
Full Changelog: agentex-sdk-v0.18.0...agentex-sdk-v0.18.1
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 patch release (0.18.1) fixes a gap in span error reporting: exceptions raised inside
Trace.span/AsyncTrace.spancontext managers were previously swallowed without being surfaced to SGP, so all spans appeared asSUCCESSeven when the body raised. The fix capturesExceptionsubclasses, records type and message ontospan.data, and propagatesstatus=ERRORthrough_build_sgp_span.span_error.py— new module withset_span_error/get_span_errorhelpers that store error metadata inspan.data[\"__error__\"]; safely no-ops onNoneand list-shaped data.trace.py— both sync and async context managers now catch, record, and re-raiseException;finallycontinues to callend_spanso span lifecycle is unchanged.sgp_tracing_processor.py—_build_sgp_spanreads the recorded error and callssgp_span.set_error(...)before returning, ensuring SGP receivesstatus=ERRORand error metadata.Confidence Score: 5/5
Safe to merge — the change is narrowly scoped to error capture in span context managers with no side effects on the happy path.
The exception path in both sync and async context managers is handled correctly: set_span_error is called before raise, and end_span still runs via finally. The get_span_error call in _build_sgp_span is guarded by a None check, so spans with no error are unaffected. BaseException subclasses like KeyboardInterrupt and asyncio.CancelledError are intentionally not captured.
No files require special attention.
Important Files Changed
Reviews (1): Last reviewed commit: "chore: release main" | Re-trigger Greptile