| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
#460) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
|
🤖 Release is at https://github.com/scaleapi/scale-agentex-python/releases/tag/agentex-client-v0.19.0 🌻 |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
✨ Stainless prepared a new release
agentex-client: 0.19.00.19.0 (2026-07-14)
Full Changelog: agentex-client-v0.18.0...agentex-client-v0.19.0
Features
Bug Fixes
- internal: resolve build failures (9245b70)
- tracing: capture span body exceptions and export SGP status=ERROR (#460) (6c23d76)
agentex-sdk: 0.19.00.19.0 (2026-07-14)
Full Changelog: agentex-sdk-v0.18.0...agentex-sdk-v0.19.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 a release PR bumping both agentex-client and agentex-sdk from 0.18.0 to 0.19.0, shipping two features and a build fix: (1) token usage is now emitted on spans for SGP billing via a new TurnSpan / turn_span() helper and per-call usage injection into LiteLLM and TemporalStreamingModel spans; (2) span body exceptions are now captured and exported as SGPStatus=ERROR.
Confidence Score: 5/5
Safe to merge — all changes are well-scoped billing/observability additions with thorough test coverage and no modifications to core workflow or data-path logic.
The PR introduces token usage recording on spans and span-level error capture. Both features follow the existing reserved-key convention in span.data, are no-ops when tracing is disabled, and are covered by dedicated unit tests. The concat_completion_chunks zip_longest fix is correct and tested. The deleted TemporalTracingModelProvider was a build-failure source; its removal is clean. No auth, data mutation, or critical control-flow paths are touched.
No files require special attention — the key billing logic in TurnSpan.record_usage and the LiteLLM usage injection are each accompanied by tests that cover the happy path, the opt-out path, and the no-usage fallback.
Important Files Changed
Reviews (3): Last reviewed commit: "chore: release main" | Re-trigger Greptile