chore(main): release 0.2.0

[github-actions]

🤖 I have created a release beep boop

0.2.0 (2026-06-23)

Features

• agent_api_keys: one-call webhook-trigger setup endpoint (#329) (9cc71fb)
• agentex-ui: grow chat input vertically for multi-line prompts (#332) (8c060f1)
• task-messages: add optional is_error to ToolResponseContent (#331) (5020e96)
• update task configs in agentex db on turn (#309) (13eea7a)

Bug Fixes

• 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)
• 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)

---

This PR was generated with Release Please. See documentation.

Greptile Summary

• Bumps release/package metadata to 0.2.0.
• Updates the generated OpenAPI spec version and formatting.
• Adds the generated 0.2.0 changelog entries.

Confidence Score: 5/5

The changes are limited to release metadata, generated API version output, and changelog updates.

No code behavior changes requiring attention were identified in the changed files.

T-Rex Logs

What T-Rex did

• Validated the baseline repository state at version 0.1.0, including OpenAPI info.version 0.1.0 and the existing webhook-trigger/is_error schema fields, with no CHANGELOG.md present.
• Validated the head state at version 0.2.0, including a CHANGELOG.md entry for 0.2.0 features, updated OpenAPI info.version 0.2.0, a webhook-trigger path, and is_error marked as optional.

_{Ran code and verified through T-Rex}

_{Reviews (7): 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.

[greptile-apps]

Update telemetry versions

This release updates the FastAPI/OpenAPI version to 0.1.1, but the OpenTelemetry defaults are still hard-coded to 0.1.0 in src/utils/otel_metrics.py for the SERVICE_VERSION fallback and get_meter(..., version="0.1.0"). In deployments that do not set SERVICE_VERSION, metrics emitted by the 0.1.1 service are tagged or scoped as 0.1.0, which breaks version-based dashboards and rollout comparisons. Please derive those defaults from src._version.__version__ or update them as part of the release bump.

Artifacts

Repro: Python harness that imports the real telemetry module with safe OpenTelemetry stubs and captures version defaults

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

Repro: harness output showing release version 0.1.1 but telemetry service.version and meter version default to 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 versions**

This release updates the FastAPI/OpenAPI version to `0.1.1`, but the OpenTelemetry defaults are still hard-coded to `0.1.0` in `src/utils/otel_metrics.py` for the `SERVICE_VERSION` fallback and `get_meter(..., version="0.1.0")`. In deployments that do not set `SERVICE_VERSION`, metrics emitted by the 0.1.1 service are tagged or scoped as 0.1.0, which breaks version-based dashboards and rollout comparisons. Please derive those defaults from `src._version.__version__` or update them as part of the release bump.

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