chore: release main

[stainless-app]

✨ Stainless prepared a new release

agentex-client: 0.25.0

0.25.0 (2026-08-24)

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

Features

• lineage: capture tool data-source refs and agent build version in span data (#469) (941bbc4)

agentex-sdk: 0.25.0

0.25.0 (2026-08-24)

Full Changelog: agentex-sdk-v0.24.0...agentex-sdk-v0.25.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

The release updates both distributions to 0.25.0 and adds lineage metadata for registered tool data sources plus agent build versions.

• Introduces the public DataSourceRef registry, decorator, resolver, merge, and recording APIs.
• Captures lineage references across harness, direct OpenAI, streaming, and Temporal execution paths.
• Adds AGENT_VERSION to exported SGP span metadata and tests the new tracing behavior.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking robustness issue in handling malformed custom lineage resolver output.

The normal lineage, packaging, and version-stamping paths are coherent, but resolver return values are processed outside the documented fail-open guard and can propagate an exception from provider completion.

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

Important Files Changed

Filename	Overview
src/agentex/lib/core/tracing/lineage.py	Adds the lineage registry and span-data helpers; malformed custom resolver output can escape the intended fail-open boundary.
src/agentex/lib/core/harness/tracer.py	Resolves registered data-source references when opening tool spans while retaining the harness-level exception guard.
src/agentex/lib/core/services/adk/providers/openai.py	Serializes completed OpenAI run items and merges resolved lineage references into span metadata.
src/agentex/lib/core/temporal/plugins/openai_agents/models/temporal_streaming_model.py	Adds lineage resolution to completed Temporal OpenAI model spans.
src/agentex/lib/core/tracing/processors/sgp_tracing_processor.py	Adds the configured agent build version to SGP span source metadata.
src/agentex/lib/environment_variables.py	Defines the optional AGENT_VERSION runtime setting.
src/agentex/lib/adk/init.py	Exposes lineage registration and data-source reference APIs through the public ADK surface.
adk/pyproject.toml	Advances the agentex-sdk package version to 0.25.0.
pyproject.toml	Advances the agentex-client package version to 0.25.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    A[Tool registration] --> B[Data-source refs and resolver]
    C[Tool or provider execution] --> D[Serialized function-call items]
    B --> E[Lineage resolution]
    D --> E
    E --> F[Merge sgp.lineage.refs into span data]
    G[AGENT_VERSION environment value] --> H[SGP processor enrichment]
    F --> I[Completed business span]
    H --> I
    I --> J[SGP export]

Loading

Prompt To Fix All With AI

### Issue 1
src/agentex/lib/core/tracing/lineage.py:117
**Resolver output escapes fail-open guard**

A custom resolver that returns a malformed reference reaches `_dedupe` outside the exception handler, where the unconditional `model_dump` call raises and propagates through provider completion. This violates lineage's fail-open contract and can turn an otherwise successful agent run into a failure.

---

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}

Greptile also left 1 inline comment on this PR.

Context used (4)

• Knowledge Base — Runtime tracing and observability
• Knowledge Base — Agent framework adapters
• Knowledge Base — Configuration, packaging, and examples
• Knowledge Base — Google ADK integration

[greptile-apps]

Resolver output escapes fail-open guard

A custom resolver that returns a malformed reference reaches _dedupe outside the exception handler, where the unconditional model_dump call raises and propagates through provider completion. This violates lineage's fail-open contract and can turn an otherwise successful agent run into a failure.

Knowledge Base Used: Runtime tracing and observability

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/agentex/lib/core/tracing/lineage.py
Line: 117

Comment:
**Resolver output escapes fail-open guard**

A custom resolver that returns a malformed reference reaches `_dedupe` outside the exception handler, where the unconditional `model_dump` call raises and propagates through provider completion. This violates lineage's fail-open contract and can turn an otherwise successful agent run into a failure.

**Knowledge Base Used:** [Runtime tracing and observability](https://app.greptile.com/scale-ai/-/custom-context/knowledge-base/scaleapi/scale-agentex-python/-/docs/runtime-tracing-and-observability.md)

---

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