[its-miso]

🤖 I have created a release beep boop

0.5.63 (2026-09-21)

Features

• deps: update dependency eslint (10.10.0 → 10.11.0) (#1035) (197c87a)
• queue: expose PR-fix work generations (#1044) (c16f04f)

Bug Fixes

• claims: gate claim/assign/status decisions on live GitHub labels (#1037) (#1042) (bacac7b)
• deps: update dependency @types/node (24.13.5 → 24.13.6) (#1036) (cb7bd79)
• deps: update dependency tsx (4.23.13 → 4.23.15) (#1039) (6555743)
• helm: update chart common (5.2.0 → 5.2.1) (#1030) (073bc93)

---

This PR was generated with Release Please. See documentation.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M3@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_low_confidence)

Recommendation

Approve. This is a release-please release PR that bumps the Dispatch application version from 0.5.62 to 0.5.63, refreshes the lockfile to match the version bump, and stages the Helm chart version / appVersion accordingly. All CI checks are green, the diff is mechanical, and the underlying dep bumps included in this release were already merged and CI-verified in their individual PRs (eslint 10.10.0 → 10.11.0, @types/node 24.13.5 → 24.13.6, tsx 4.23.13 → 4.23.15, helm chart common 5.2.0 → 5.2.1), plus the feature PR exposing PR-fix generations and the claims live-label-gate PR. No application code is modified by this release PR itself.

Change-by-change findings

• .release-please-manifest.json: Only the version string changes (0.5.62 → 0.5.63). No semantic content otherwise.
• CHANGELOG.md: Insertion of a single new section for 0.5.63 with two features and four bug fixes. Consistent with the contributing PRs and prior release shape. No reformatting of earlier sections.
• charts/dispatch/Chart.yaml: version and appVersion both bump 0.5.62 → 0.5.63, keeping them in lockstep with the app (this is the same pattern as v0.5.62 and earlier — repository convention observed).
• package-lock.json: Only the top-level name/version metadata bump. Notably the lockfile entries for eslint 10.11.0 and the previous bump range are already pinned, consistent with the cumulative release contents (no new transitive resolutions introduced by this release PR).
• package.json: Single-field version bump; engines.node: >=24, dependencies, and scripts untouched.

Required checks (must-check items)

• Breaking API changes in updated dependencies: The four dep-related deltas included in this release are all patch-level: eslint patch (10.10.0 → 10.11.0), @types/node patch (24.13.5 → 24.13.6), tsx patch (4.23.13 → 4.23.15), and the helm chart common patch (5.2.0 → 5.2.1). Each was independently merged and shipped in the constituent PRs; the dep bumps do not cross a major boundary. The release PR itself does not introduce any new dependency resolution. Patch-level changes for @types/node and eslint are well-known to be low-risk for callers at the type/lint boundary, and tsx patch bumps keep the same runtime entry points. No breaking API or signature changes are introduced by this PR. ✅

• Run full test suite after upgrade: The CI status table reports Tests: success, plus Build, Typecheck, Lint, npm audit, Database migrations, Database integration, smoke, Coverage, Docker Build, and Docker Build (MCP) all green against the release commit 16669aba. The release PR carries the exact dependency lockfile + manifest state as the merged constituent PRs (which themselves were CI-verified), and CI reruns the full suite on this merge. ✅

Standalone verification — package.json engines.node: >=24 ↔ @types/node 24.13.6

engines.node: >=24 is an active obligation across this repo (per AGENTS.md "Tech Stack" / Dockerfile base node:24-bookworm-slim). The bundled @types/node is now 24.13.6, which is a same-major (24.x) patch that satisfies the engine constraint. No host-platform compatibility ambiguity: this is in-language type bindings, no host OS, no chart, no embedded runtime version is pinned elsewhere that needs cross-checking.

Standards Compliance

The release-please workflow is the documented release mechanism for this repo (.github/workflows/release-please.yaml). The diff matches the convention seen in v0.5.62 (compare metadata for v0.5.61…v0.5.62):

• Five-file mechanical release (manifest, CHANGELOG, Chart version/appVersion, package-lock name/version, package.json version).
• Helm chart version and appVersion bumped together, matching repo history.

No AGENTS.md conventions are violated: engines.node: >=24 preserved; no agent-specific names appear in generated docs; no secrets are touched; Docker / Prisma / next.js version surfaces are untouched.

A sub-check against the Requirement Ledger:

• req-e589bfe1ad7c — "Lint/typecheck blocks CI; must pass": CI shows Lint: success and Typecheck: success. Satisfied (diff: package-lock.json lint surfaces; tool: CI).
• req-ad902b2a08da — "Tokens are secrets … must never be logged, echoed, or persisted": this PR does not log or persist any tokens; only version strings change. Satisfied (diff: no token surface; tool: CI green including npm audit).

Unknowns or Needs Verification

• The reviewer could not fetch the v0.5.62…v0.5.63 GitHub compare page (tool returned "Could not fetch compare metadata"). This does not affect the review because the full PR diff, CI status, CHANGELOG entries, and component commits are all directly present in the corpus. No further fetch needed.
• Linked issue bodies for issues PR 1030, PR 1035, PR 1036, PR 1037, PR 1039, PR 1042, PR 1044 were not fetched by the harness (all GitHub HTML pages were skipped). The PR release notes, component commit SHAs, and CI results are sufficient to attest the dep and feature deltas shipped in this release.

Sources

• PR diff (this corpus): .release-please-manifest.json, CHANGELOG.md, charts/dispatch/Chart.yaml, package-lock.json, package.json.
• CI status (this corpus): all green against commit 16669aba.
• AGENTS.md (this corpus): release conventions, env/script conventions, lint/typecheck obligation, secrets handling.
• Prior release compare metadata (this corpus, Source 10): confirms the same five-file mechanical release pattern was used for v0.5.62.

[its-miso]

🤖 Created releases:

• v0.5.63

🌻