release: 0.22.1

[seratch]

Release readiness review (v0.22.0 -> TARGET release/v0.22.1)

This is a release readiness report done by $final-release-review skill.

Diff

v0.22.0...5c67dd0

Release intent

• Review mode: final candidate
• Intended release: patch, v0.22.1
• Minimum required release type: patch
• Versioning verdict: compatible

Release call

🟢 GREEN LIGHT TO SHIP The candidate is consistently versioned as v0.22.1, preserves released compatibility boundaries, and has no confirmed release-blocking regression.

Scope summary

• 183 files changed (+8,482/-2,691); key areas touched include model and provider behavior, Voice APIs, MCP lifecycle management, sandbox state, tracing and usage accounting, tests, documentation, and release metadata.

Risk assessment (ordered by impact)

1. OpenAI client ownership and Voice API contracts

   • Risk: 🟢 LOW. The release expands and corrects Voice configuration behavior without removing the v0.22.0 public API or changing existing positional argument meaning.
   • Evidence: The BASE-versus-TARGET public contract comparison found no removed exports. The prospective contract was validated from built wheel and source-distribution artifacts, including optional Voice dependencies.
   • Files: src/agents/voice/, tests/voice/, tests/fixtures/released_api_contract.json
   • Action: No additional release action is required. Preserve the frozen v0.22.1 contract and rerun the gate if the candidate changes.

2. Model terminal-state, request-body, and approval behavior

   • Risk: 🟢 LOW. The changes correct reachable error and retry behavior while retaining supported partial-output, refusal, tool-call, tracing, and usage paths.
   • Evidence: The release range adds targeted handling and regression coverage for truncation, provider request bodies, callable approval failures, and failed-attempt accounting rather than introducing a new provider contract.
   • Files: src/agents/models/, src/agents/run_internal/, tests/models/, tests/
   • Action: No additional release action is required. Treat changes to these paths after this review as invalidating the release call.

3. MCP cache isolation and cleanup lifecycle

   • Risk: 🟢 LOW. MCP cleanup now refreshes active-server state while preserving cancellation propagation and connection ownership.
   • Evidence: The latest runtime fix clears the active MCP server view after cleanup, including failure paths, and adds focused lifecycle coverage. No released serialization or transport contract is removed.
   • Files: src/agents/mcp/, tests/mcp/
   • Action: No additional release action is required.

4. Sandbox labels and persisted run state

   • Risk: 🟢 LOW. The release adds trusted Docker sandbox label handling while retaining compatibility for supported persisted state and resume behavior.
   • Evidence: Label resolution remains owned by trusted current configuration, and compatibility checks cover create, resume, replacement, reuse, and packaged optional-dependency installations.
   • Files: src/agents/extensions/sandbox/, tests/extensions/sandbox/
   • Action: No additional release action is required. Preserve the current schema and trust-boundary tests.

5. Translated documentation heading anchors

   • Risk: 🟢 LOW. Explicit heading-anchor synchronization does not affect runtime behavior, packaging, or the public API contract.
   • Evidence: The final main commit changes only 102 files under the Japanese, Korean, and Chinese documentation trees, with matching heading-anchor replacements.
   • Files: docs/ja/, docs/ko/, docs/zh/
   • Action: No additional release action is required.

Documentation coverage (non-blocking)

• Coverage source: docs: document v0.22.1 behavior updates #4577 at a6861ef5184d0d5705016e0be5badd3b13368238
• Status: covered
• Covered obligations: OpenAI client precedence; Voice STT and TTS configuration; Docker sandbox labels; callable approval failures; MCP cache isolation; model truncation and request-body behavior; trace flushing; usage aggregation isolation; visualization node identity
• Gaps or post-release suggestions: none
• Publication timing: Keep docs: document v0.22.1 behavior updates #4577 unmerged until v0.22.1 is available because it documents behavior not present in v0.22.0.

Notes

• The candidate checkout is clean at 5c67dd0a5390e1333216c72ecc01d73ca8386d30 on release/v0.22.1.
• pyproject.toml, uv.lock, the branch name, and the released API contract consistently declare v0.22.1.
• The release commit contains only pyproject.toml, uv.lock, and tests/fixtures/released_api_contract.json.
• The contract baseline commit and candidate parent both resolve to 7f7a44f8dc0650296bd5ab6c745c9bcbaa6ac3b7.
• Any subsequent change to the candidate, its base, version metadata, lockfile, or contract invalidates this release call.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-22T13:38:23.221752Z	5c67dd0	New commits
🔒 Security Review	✅ Completed 2026-08-22T13:37:50.372888Z	5c67dd0	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9b14fff3dd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".