Skip to content

chore: release main - #492

Open
stainless-app[bot] wants to merge 5 commits into
mainfrom
release-please--branches--main--changes--next
Open

chore: release main#492
stainless-app[bot] wants to merge 5 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

✨ Stainless prepared a new release

agentex-client: 0.24.0

0.24.0 (2026-08-11)

Full Changelog: agentex-client-v0.23.0...agentex-client-v0.24.0

Features

  • tracing: per-step obs wrappers inside business Temporal activities (#491) (5c7ee10)
agentex-sdk: 0.24.0

0.24.0 (2026-08-11)

Full Changelog: agentex-sdk-v0.23.0...agentex-sdk-v0.24.0

Chores

  • agentex-sdk: Synchronize agentex versions

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 release advances both packages to 0.24.0 and adds per-step observability wrappers inside business Temporal activities.

  • Selects OTel-backed wrappers for Temporal business activities while retaining ambient-span tagging for dispatched start/end activities.
  • Adds backend-drift warnings and focused tracing regression tests.
  • Updates package manifests, generated version metadata, statistics, and changelogs.

Confidence Score: 4/5

The PR appears safe to merge, with only a non-blocking requirement to link the new tracing TODO to a tracked ticket.

The Temporal tracing branches keep locally opened wrappers closable in the same process, and no blocking tracing or release-version failure remains; the accepted concern is limited to follow-up-work tracking.

Files Needing Attention: src/agentex/lib/core/tracing/trace.py

Important Files Changed

Filename Overview
src/agentex/lib/core/tracing/trace.py Distinguishes tracing-dispatch activities from business activities so only locally closable per-step wrappers are opened; the new follow-up TODO lacks required ticket tracking.
src/agentex/lib/core/tracing/obs_span.py Adds OTel-first wrapper creation and ambient tagging when the caller expects a Temporal OTel context.
src/agentex/lib/core/tracing/obs_ids.py Renames the backend preference parameter and adds deduplicated warnings when configured and active observability backends differ.
tests/test_temporal_obs_backend.py Adds regression coverage for dispatch classification, business-activity wrapper selection, OTel correlation, and backend-drift warning deduplication.
pyproject.toml Advances the agentex-client release version from 0.23.0 to 0.24.0.
adk/pyproject.toml Advances the agentex-sdk overlay release version from 0.23.0 to 0.24.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Begin business span] --> B{SDK tracing dispatch activity?}
    B -- Yes --> C[Tag ambient OTel activity span]
    C --> D[Persist ambient correlation IDs]
    B -- No --> E{Inside any Temporal activity?}
    E -- Yes --> F[Open per-step OTel wrapper]
    E -- No --> G[Open backend selected by mode]
    F --> H[Register wrapper handle]
    G --> H
    H --> I[End business span locally]
    I --> J[Pop and close wrapper handle]
Loading

Fix All in Cursor Fix All in Claude Code Fix All in Codex

Prompt To Fix All With AI
### Issue 1
src/agentex/lib/core/tracing/trace.py:200-208
**Untracked tracing follow-up TODO**

This TODO leaves the retry roll-up and multi-replica validation work under a generic `obs-followup` label without the required ticket number or Linear link, making the deferred work difficult to locate and track.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "chore: release main" | Re-trigger Greptile

Context used:

  • Rule used - Include ticket numbers in TODO comments to make cl... (source)

Learned From
scaleapi/scaleapi#126926

  • Rule used - Create Linear tasks for TODO comments in code and ... (source)

Learned From
scaleapi/scaleapi#127117

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant