chore(main): release 0.2.0

[github-actions]

🤖 I have created a release beep boop

0.2.0 (2026-07-13)

Features

• agent_api_keys: one-call webhook-trigger setup endpoint (#329) (9cc71fb)
• agentex-ui: account picker via same-origin BFF proxy (#350) (0f07dc7)
• agentex-ui: grow chat input vertically for multi-line prompts (#332) (8c060f1)
• agentex-ui: OIDC login with server-side access token (#351) (824286c)
• retention: strict bool env parsing + stale-RUNNING cleanup override (#306) (5ad81e8)
• schedules: add exact skip and unskip actions (#357) (ac88134)
• schedules: agent run schedules (v1) (#335) (6a66ad3)
• task-messages: add optional is_error to ToolResponseContent (#331) (5020e96)
• update task configs in agentex db on turn (#309) (13eea7a)

Bug Fixes

• agentex-ui: merge URL updates against the live URL to fix account-switch races (#355) (f87e363)
• agentex-ui: stop clipping agent badge hover scale and shadow (#352) (b49fab6)
• agentex: bump aiohttp 3.13.4 -> 3.14.1 (clears 11 CVEs, agentex server image) (#359) (3001351)
• authz: grant legacy agent register principal (#325) (cae5f94)
• deps: cap fastapi <0.137.0 to stop OPTIONS preflight 500s (#334) (acbe9e3)
• deps: clear golden-image Trivy CRITICAL/HIGH (litellm, starlette, pyjwt, python-multipart) (#320) (bfa6652)
• page ready agents during health-check startup (#345) (2ffde24)
• schedules: backfill agent_run_schedules deleted_at/version on early-deployed envs (#341) (fc1ba55)
• schedules: grant legacy auth for run schedules (#344) (648e81c)
• schedules: use stable handles for run schedules (#349) (3b722f6)
• streams: cut SSE error-log volume and add Redis pool headroom (#340) (352eaaa)
• streams: snapshot SSE cursor before "connected" to stop first-token drops (#330) (7c2ccfd)
• tasks: preserve task_metadata in combined update and forward merge_params by name (#336) (8c25c64)
• ui: load all agents so the picker and deep-links work past the first page (#347) (92b9da3)

Documentation

• document Redis as a required dependency (#343) (4c1740b)
• guides: tracing, framework-agent, and local-sandbox guides (#339) (b43e8c3)
• streaming: document the unified harness surface (#337) (31fd697)

---

This PR was generated with Release Please. See documentation.

Greptile Summary

This is a release-please-generated PR that cuts the 0.2.0 release, bundling ~20 merged features and fixes (schedules, OIDC login, account picker, SSE improvements, aiohttp CVE patch, and more) into version and changelog artifacts.

• Version is bumped to 0.2.0 in _version.py, both pyproject.toml files, openapi.yaml, and .release-please-manifest.json.
• The root pyproject.toml raises the aiohttp override floor to >=3.14.1 to clear 11 CVEs, but agentex/pyproject.toml's direct constraint remains >=3.10.9,<4, leaving standalone installs of agentex-backend exposed to those same CVEs.
• uv.lock still records both workspace packages as 0.1.0 and would need regeneration for a fully consistent release artifact.

Confidence Score: 4/5

Safe to merge for workspace/Docker deployments; one incomplete security fix in the member package direct dependency is worth addressing before wider distribution.

The aiohttp CVE fix is only enforced through the workspace override in the root pyproject.toml. The agentex/pyproject.toml direct constraint still allows versions back to 3.10.9, so any out-of-workspace install of agentex-backend can resolve a vulnerable version. All other changes are clean version bumps and generated artifacts.

agentex/pyproject.toml — the aiohttp floor needs to be raised from >=3.10.9 to >=3.14.1 to match the workspace override and keep the CVE fix effective for all install paths.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version manifest updated from 0.1.0 to 0.2.0; straightforward release-please bookkeeping.
CHANGELOG.md	New CHANGELOG.md created by release-please, listing all features, fixes, and docs for 0.2.0.
agentex/src/_version.py	Version string bumped to 0.2.0; single-line change.
pyproject.toml	Root workspace version bumped to 0.2.0; aiohttp override floor raised to >=3.14.1 to clear CVEs.
agentex/pyproject.toml	Version bumped to 0.2.0, fastapi cap kept at <0.137.0. aiohttp direct dep still at >=3.10.9 while the security-patched minimum is 3.14.1 — standalone installs of this package could resolve a vulnerable version.
agentex/openapi.yaml	OpenAPI spec version bumped to 0.2.0 with new schedule skip/unskip endpoints, webhook trigger endpoint, and task-message schema additions that match the listed features.

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

[greptile-apps]

Regenerate the lockfile

The package versions were bumped here and in agentex/pyproject.toml, but uv.lock still records both workspace packages as 0.1.0 (agentex and agentex-backend). The Docker build copies that lockfile and runs uv sync --frozen --no-dev --package agentex-backend and uv export --frozen, so the release image path can fail the frozen-lock freshness check or install/export package metadata from the previous version. Regenerate and commit uv.lock with the 0.1.1 package versions.

Artifacts

Repro: lock metadata check script

• Contains supporting evidence from the run (text/x-python; charset=utf-8).

Repro: lock metadata check output showing stale package versions

• Keeps the command output available without making the summary code-heavy.

Repro: attempted frozen uv sync command output

• Keeps the command output available without making the summary code-heavy.

Repro: attempted frozen uv export command output

• Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: pyproject.toml
Line: 3

Comment:
**Regenerate the lockfile**

The package versions were bumped here and in `agentex/pyproject.toml`, but `uv.lock` still records both workspace packages as `0.1.0` (`agentex` and `agentex-backend`). The Docker build copies that lockfile and runs `uv sync --frozen --no-dev --package agentex-backend` and `uv export --frozen`, so the release image path can fail the frozen-lock freshness check or install/export package metadata from the previous version. Regenerate and commit `uv.lock` with the `0.1.1` package versions.

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

[github-actions]

✱ Stainless preview builds

This PR will update the agentex-sdk SDKs with the following commit messages.

openapi

chore(main): release 0.2.0

python

chore(main): release 0.2.0

typescript

chore(internal): regenerate SDK with no functional changes

Edit this comment to update them. They will appear in their respective SDK's changelogs.

✅ agentex-sdk-openapi studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅

✅ agentex-sdk-typescript studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️ → build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ✅) → test ✅

⚡ agentex-sdk-python studio · conflict

Your SDK build resulted in a merge conflict between your custom code and the newly generated changes, which is a regression from the base state.
You don't need to resolve this conflict right now, but you will need to resolve it for your changes to be released to your users. Read more about why this happened here.

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-06-25 18:06:43 UTC

[greptile-apps]

Regenerate frozen lockfile

This release bumps the workspace package to 0.2.0, but uv.lock still records both agentex and agentex-backend as 0.1.0. The Docker image copies that lockfile and runs frozen uv export / uv sync for agentex-backend, so the release build can fail the frozen-lock check or install/export package metadata for the previous version instead of this release.

Artifacts

Repro: generated frozen uv check script

• Contains supporting evidence from the run (text/x-shellscript; charset=utf-8).

Repro: frozen uv command output showing stale lockfile validation failure

• Keeps the command output available without making the summary code-heavy.

Repro: uv 0.7.3 installation output used to run the frozen checks

• Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: pyproject.toml
Line: 3

Comment:
**Regenerate frozen lockfile**

This release bumps the workspace package to `0.2.0`, but `uv.lock` still records both `agentex` and `agentex-backend` as `0.1.0`. The Docker image copies that lockfile and runs frozen `uv export` / `uv sync` for `agentex-backend`, so the release build can fail the frozen-lock check or install/export package metadata for the previous version instead of this release.

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

[greptile-apps]

Update telemetry version defaults

The API version now comes from __version__ and is 0.2.0, but src/utils/otel_metrics.py still falls back to SERVICE_VERSION 0.1.0 and get_meter(..., version="0.1.0"). Internal callers use get_meter without passing a version, so deployments that do not set SERVICE_VERSION emit 0.2.0 service metrics under the old 0.1.0 version, which can make rollout dashboards and version comparisons incorrect.

Artifacts

Repro: Python harness that exercises telemetry version defaults with SERVICE_VERSION unset

• Contains supporting evidence from the run (text/x-python; charset=utf-8).

Repro: harness output showing package version 0.2.0 but telemetry resource and meter version 0.1.0

• Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: agentex/src/_version.py
Line: 3

Comment:
**Update telemetry version defaults**

The API version now comes from `__version__` and is `0.2.0`, but `src/utils/otel_metrics.py` still falls back to `SERVICE_VERSION` `0.1.0` and `get_meter(..., version="0.1.0")`. Internal callers use `get_meter` without passing a version, so deployments that do not set `SERVICE_VERSION` emit 0.2.0 service metrics under the old 0.1.0 version, which can make rollout dashboards and version comparisons incorrect.

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