release: 0.9.3

[its-miso]

🤖 I have created a release beep boop

0.9.3 (2026-09-17)

Bug Fixes

• bridge: cap the retry path by CODER_AGENT_SLOTS + share coder load across the tick (#344) (6032d28)

---

This PR was generated with Release Please. See documentation.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — primary route

PR Review: release: 0.9.3 (PR PR 345)

Recommendation

Approve. This is a Release Please-generated release commit that bumps the project version from 0.9.2 → 0.9.3 and records the CHANGELOG entry. The actual bug-fix code (from PR 344: "cap the retry path by CODER_AGENT_SLOTS + share coder load across the tick") is already present on main at commit 6032d28; this release branch (release-please--branches--main) will include it in the tagged artifact. No dependency changes are present in the diff, and CI has confirmed all checks pass.

---

Required Checks

check for breaking API changes in updated dependencies

Not applicable. This PR contains zero dependency changes. The diff only touches three files:

• .release-please-manifest.json: version 0.9.2 → 0.9.3
• CHANGELOG.md: addition of the 0.9.3 release header and bug-fix entry
• pyproject.toml: version = "0.9.2" → version = "0.9.3"

No requirements.txt, requirements-dev.txt, or other dependency pins are modified. There are no upstream dependency bumps to evaluate for breaking API changes.

run full test suite after upgrade

Verified — CI test check passed. The CI check results table shows test: success for commit aac223b. No breaking test regressions are present in the corpus.

---

Change-by-Change Summary

File	Change	Assessment
.release-please-manifest.json	0.9.2 → 0.9.3	Correct. Synced with pyproject.toml version.
CHANGELOG.md	Prepended 0.9.3 section citing fix PR 344 (6032d28)	Correct. Release Please format; references the actual fix commit on main.
pyproject.toml	version = "0.9.2" → version = "0.9.3"	Correct. Matches manifest version.

---

Standards Compliance

The repository's AGENTS.md convention on issue filing (imperative-sentence ask, named file paths) applies to issue authors, not to Release Please automation. Release Please is a well-known tool (per Source 1/2 in Linked Sources) and its mechanical version-bump commits follow the project's own release-please.yaml workflow. No repository convention conflicts detected.

---

Tool Harness Findings

No tool calls were issued; reviewing corpus directly. No discrepancies found.

---

Unknowns / Needs Verification

None. The release is mechanically clean, CI is green, and the underlying fix is already on main. The dependency_upgrade classification does not match the diff content (no dependencies are upgraded), but this is a classifier output, not a blocking issue — there is nothing in the diff that requires dependency-compatibility verification.

[its-miso]

🤖 Created releases:

• v0.9.3

🌻