chore: release main

[stainless-app]

✨ Stainless prepared a new release

agentex-client: 0.14.0

0.14.0 (2026-06-18)

Full Changelog: agentex-client-v0.13.1...agentex-client-v0.14.0

Features

• compat: runtime SDK↔backend version guard at ACP startup (#408) (433c999)

---

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

• Bumps agentex-client to 0.14.0 and updates the release metadata and changelog.
• Adds a backend compatibility/version guard that reads /openapi.json.
• Wires the guard into FastACP server startup and Temporal worker registration.
• Adds tests covering version parsing, guard behavior, and worker startup ordering.

Confidence Score: 4/5

The runtime guard changes are narrowly scoped, but the release metadata needs attention before merging because the package containing the new guard is not being released alongside the advertised client update.

The changed code is covered by focused tests and the packaging mismatch is concrete and localized to release metadata, making the main merge risk clear.

.release-please-manifest.json and the ADK/package metadata should be aligned so the package containing the guard is released with the client update.

T-Rex Logs

What T-Rex did

• Reproduced packaging metadata behavior by running a focused inspection script that parsed the release manifest, root pyproject, ADK pyproject, and the ADK build hook, showing agentex-client excludes src/agentex/lib/** from its wheel and ADK remains 0.13.1 with its lib-including build hook.
• Validated the first worker-guard flow by running a test where a registration POST occurred initially, but after head GET /openapi.json the process raised IncompatibleBackendError with EXIT_CODE 2 and no registration POST occurred on head.
• Validated the second worker-guard flow, confirming the changed guard behavior: after a head GET /openapi.json an IncompatibleBackendError is raised and the process exits with EXIT_CODE 42, with no packaging surface evaluated or reported.

_{Ran code and verified through T-Rex}

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
.release-please-manifest.json:3
**Release skips ADK**

The new runtime guard is implemented under `src/agentex/lib`, but the root `agentex-client` wheel excludes `src/agentex/lib/**`; those files ship from the `agentex-sdk`/ADK package instead. This manifest bumps only the root client package while leaving `adk` at `0.13.1`, and the ADK package metadata still points at `agentex-sdk` `0.13.1`, so publishing this release can advertise the startup version guard without publishing the package that contains `BaseACPServer`, `AgentexWorker`, or `compat.version_guard`. Users upgrading the ADK package would still run without the guard. Please release/bump the ADK package for this change as well, and keep its client dependency aligned if it depends on the co-released client version.

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

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Release skips ADK

The new runtime guard is implemented under src/agentex/lib, but the root agentex-client wheel excludes src/agentex/lib/**; those files ship from the agentex-sdk/ADK package instead. This manifest bumps only the root client package while leaving adk at 0.13.1, and the ADK package metadata still points at agentex-sdk 0.13.1, so publishing this release can advertise the startup version guard without publishing the package that contains BaseACPServer, AgentexWorker, or compat.version_guard. Users upgrading the ADK package would still run without the guard. Please release/bump the ADK package for this change as well, and keep its client dependency aligned if it depends on the co-released client version.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .release-please-manifest.json
Line: 3

Comment:
**Release skips ADK**

The new runtime guard is implemented under `src/agentex/lib`, but the root `agentex-client` wheel excludes `src/agentex/lib/**`; those files ship from the `agentex-sdk`/ADK package instead. This manifest bumps only the root client package while leaving `adk` at `0.13.1`, and the ADK package metadata still points at `agentex-sdk` `0.13.1`, so publishing this release can advertise the startup version guard without publishing the package that contains `BaseACPServer`, `AgentexWorker`, or `compat.version_guard`. Users upgrading the ADK package would still run without the guard. Please release/bump the ADK package for this change as well, and keep its client dependency aligned if it depends on the co-released client version.

How can I resolve this? If you propose a fix, please make it concise.