release: 0.5.69

[its-miso]

🤖 I have created a release beep boop

0.5.69 (2026-10-12)

Features

• auth: bind worker bearer tokens to agent names (#1129) (#1207) (616dbd1)
• deps: update dependency @radix-ui/react-slot (1.4.0 → 1.5.0) (#1228) (38ca2c7)
• deps: update dependency lucide-react (1.52.0 → 1.53.0) (#1196) (99c93f5)
• deps: update dependency lucide-react (1.53.0 → 1.54.0) (#1208) (7ee3e66)
• deps: update dependency lucide-react (1.54.0 → 1.55.0) (#1213) (ab41eac)
• helm: update chart common (5.2.1 → 5.3.0) (#1216) (3c61ef8)
• pr-fix: accept external waits without charging fix attempts (#1233) (6888ff3)
• report: accept already_done that closes an issue via the close policy (#1143) (#1219) (7ae2b38)

Bug Fixes

• deps: update dependency @types/node (24.19.1 → 24.19.2) (#1209) (7ae16a4)
• deps: update dependency zod (4.6.5 → 4.6.6) (#1223) (f1a3058)
• deps: update dependency zod (4.6.6 → 4.6.7) (#1234) (9d59419)
• deps: update vitest monorepo (5.0.3 → 5.0.4) (#1232) (b5f69da)
• dispatch: retire external groom task dispatch (#1200) (#1201) (e7ac005)
• groomer: gate contributor-facing replies to external users (#1198) (#1199) (b42cecf)
• groomer: guard already_done closes against reopen/regression evidence (#1204) (89e1b78)
• groomer: sanitize GitHub-authored error text at mutation errorMessage helpers (#1164) (#1215) (366edf9)
• helm: decouple liveness from database availability (#1171) (#1235) (c8d9b93)
• pr-fix: reclaim unacknowledged hand-outs safely (#1211) (#1212) (8a9b642)
• pr-fix: separate human decisions from retry exhaustion (#1218) (#1221) (60c8213)
• pr-fix: skip explicitly consumed generations (#1225) (#1227) (bf090c3)
• report: restrict already_done to issue implementation (#1229) (#1230) (fd6bc88)
• tasks: accept neutral handed-off reports (#1224) (#1226) (685fcd2)

---

This PR was generated with Release Please. See documentation.

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M3 (anthropic) — primary route · pr-reviewer-action v3.4.1

Recommendation

Approve. This is a release-please bot PR for v0.5.69 carrying the standard version-bump set (.release-please-manifest.json, package.json, package-lock.json, charts/dispatch/Chart.yaml, and CHANGELOG.md). No source code changes. The only material signal inside the diff is the bundled common chart bump (5.2.1 → 5.3.0) and the dependency changelog entries, both of which were reviewed in the individual PRs that this release aggregates.

Change-by-change findings

• .release-please-manifest.json — bumps the release-please root version from 0.5.68 to 0.5.69. Single-line, expected.
• package.json — only the top-level "version" field changes; the dependencies, devDependencies, engines, overrides, and // rationale blocks are untouched. Confirmed by the diff and by reading the post-change file.
• package-lock.json — only the package's own version field is updated in two places (root and the packages."" block). No transitive resolution changes. Safe.
• charts/dispatch/Chart.yaml — chart version and appVersion both bumped to 0.5.69. The common library dependency pin sits at 5.3.0, which the merged PR PR 1216 already vetted; Chart.lock (sha256:33abae9…) was regenerated for that version. The values API the dispatch chart consumes (controllers.main.containers.main.probes, route.main, migrations, etc.) follows the bjw-s common 5.x shape and the project's values.yaml already documents the same shape, so the 5.2.1 → 5.3.0 minor bump is covered by the chart's own helm dependency build + helm lint + helm template gates in .github/workflows/helm-lint.yaml. No signature changes are apparent on the consumed values.
• CHANGELOG.md — aggregates the merged conventional-commit history into a single 0.5.69 release section. Every entry is one of the already-merged PRs in the corpus.

Tool Harness Findings

• The chart-common host-platform fetch (raw.githubusercontent.com/bjw-s/...) was refused by the allowlist and the docs site (bjw-s-labs.github.io) was also off-allowlist, so the bjw-s common 5.3.0 release notes / API-compat matrix could not be pulled directly. Indirect signals (digest-pinned Chart.lock regenerated for 5.3.0, and the chart helm dependency build + helm lint + helm template CI runs all passing) confirm the bump resolves and renders. The dispatch values surface used (probes + route + migrations Job) is documented in the repo's own values.yaml against the same bjw-s common API and was already exercised in the v0.5.68 release; the 5.2.1 → 5.3.0 step is a minor-version bump within the same major, so any signature change would be visible in the rendered probes check that runs in CI.
• release-please config file (.release-please-config.json) was not present in the repo tree, but the diff and merged history are consistent with the googleapis/release-please bot's standard behavior (the head branch is release-please--branches--main--components--dispatch, matching the project's per-component release-please convention noted in AGENTS.md).

Standards Compliance

• AGENTS.md "Release / version drift" is in the NORMAL lane by the repository's own lane-classification guidance; this PR is exactly that: a version-bump release. The CI requirements in AGENTS.md ("Lint/typecheck blocks CI; must pass") are satisfied by the green CI row block.
• No secrets, tokens, or env values are touched by the diff, so the "Tokens are secrets" rule is trivially upheld.
• The release-please v0.5.68 tag exists in repo history and the immediately preceding commit is the fix(helm) decouple-liveness (PR 1171 / PR 1235) PR, matching the version-history evidence.

Unknowns or Needs Verification

• A direct bjw-s common 5.3.0 changelog/compat-matrix page was unreachable from this environment; the bjw-s docs host and raw GitHub were not on the fetch allowlist. Compatibility is inferred from the project's own helm-lint/template CI passing for 5.3.0 and from the values surface being stable across 5.2.1 → 5.3.0, which is the same evidence path used when the previous minor bump landed. No blocker.

Notes on must_check items

• "check for breaking API changes in updated dependencies" — the only updated runtime dependency carried by this PR is the bjw-s common chart 5.2.1 → 5.3.0; the chart's helm-lint + helm template + probe-shape checks all pass, and the dispatch values consumed by the common library (controllers.main.containers.main.probes.{liveness,readiness}, service.main, route.main, and the migrations Job) are unchanged in shape. The npm dependency versions that will ship with this release were each individually landed in prior PRs (radix-ui/react-slot 1.4.0→1.5.0, lucide-react 1.52.0→1.53.0→1.54.0→1.55.0, @​types/node 24.19.1→24.19.2, zod 4.6.5→4.6.6→4.6.7, vitest 5.0.3→5.0.4) and the CI suite passes against the head commit. Patch-level changes inside a single major are not breaking by npm semver policy.
• "run full test suite after upgrade" — the head commit has all CI checks green (Tests, Coverage, Database migrations, Database integration, smoke, Typecheck, Lint, Build, Docker Build, Docker Build (MCP), npm audit, Workflow lint).

[its-miso]

🤖 Created releases:

• v0.5.69

🌻