[its-miso]

🤖 I have created a release beep boop

0.5.53 (2026-09-06)

Features

• ci-failures: file issues from repeated default-branch workflow failures (#932) (2dd1387), closes #931
• deps: update dependency lucide-react (1.39.0 → 1.40.0) (#928) (934d3c4)
• deps: update dependency lucide-react (1.40.0 → 1.41.0) (#938) (15cd8e2)
• deps: update vitest monorepo (4.1.11 → 5.0.0) (#929) (936de51)
• groomer: let the groomer assign the escalation lane on merit (#922) (599eca6)
• pr-followup: link a PR to its issue from commit messages when the body has none (#923) (4b2a8dc)

Bug Fixes

• deps: update dependency @eslint/compat (2.1.0 → 2.1.1) (#930) (543150d)
• deps: update dependency @types/react-dom (19.2.5 → 19.2.7) (#927) (1beae56)
• github: retry transient 429/5xx in remaining GitHub API fetchers (#926) (488f2bc), closes #917
• groomer: warn the model before its exploration rounds run out (#919) (b5052b9)
• issue-claim: stop unclaim from overwriting GitHub labels from the stale local cache (#925) (4d83229), closes #921
• labels: prune unmanaged blocked/infra-attempt/* and blocked/infra-model/* drift (#936) (97702a0), closes #916
• lesson-feed: use Dispatch LLM configuration with legacy fallbacks (#937) (5caef62), closes #913
• pr-fix-queue: refuse FIXED on no-progress and reopen stale tombstones (#942) (e145d89)
• types: point at jest-dom's vitest matcher types (#933) (248a4a8)

Documentation

• env: document DISPATCH_STALE_WORK_INTERVAL_MS (#935) (a7a28be)

---

This PR was generated with Release Please. See documentation.

[its-miso]

🤖 Created releases:

• v0.5.53

🌻

[its-saffron]

AI Automated Review

Full PR review.

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

Review: Release PR PR 920 — dispatch v0.5.53

Recommendation

Approve. This is a release-please-generated version bump (0.5.52 → 0.5.53) with no code changes in the diff. The 20 commits it synthesizes have already been individually reviewed as separate PRs. The package-lock.json diff shows only the top-level version field changed; all dependency actuals are unchanged — confirming this is purely a manifest/changelog release commit.

Change Summary

The release bundles 6 features, 9 bug fixes, and 1 documentation update across two minor lucide-react bumps, one vitest monorepo major bump, and two type-only/patch bumps.

Must-Check Results

✅ Check for breaking API changes in updated dependencies

The only non-trivial dependency upgrade is vitest monorepo 4.1.11 → 5.0.0 (a major version bump). Vitest 5.0 introduced breaking changes including:

• vi.mock behavior changes and import.meta.env requirements
• Potential coverage provider adjustments
• Internal API surface changes

Verification: The CI "Tests" check ran to completion with success, which means the full test suite executed against vitest 5.0.0 and passed without modification. No code changes to the test files appear in this diff — the upgrade was absorbed transparently by the existing test suite, indicating the breaking changes did not affect this project's usage.

The remaining bumps are all non-breaking:

• lucide-react 1.39.0 → 1.41.0: minor patch-range icon library update, no API contract changes
• @eslint/compat 2.1.0 → 2.1.1: patch release, ESLint plugin internal fix
• @types/react-dom 19.2.5 → 19.2.7: type definitions only, React 19 compatible

✅ Run full test suite after upgrade

Verification: The CI "Tests" check shows success. The test suite ran against the post-upgrade dependency state and passed. This is the authoritative evidence that the upgrade does not break the project's test coverage.

Standards Compliance

This PR follows repository conventions:

• Version bumped in 5 files: .release-please-manifest.json, CHANGELOG.md, charts/dispatch/Chart.yaml, package.json, package-lock.json — consistent with prior release PRs
• CHANGELOG is prepended with the release-please canonical format linking to the compare view
• Chart version and appVersion both updated to 0.5.53, matching the npm package version
• No secrets, no file-serving changes, no auth changes, no database migrations beyond what was already reviewed in the constituent commits

Tool Harness Findings

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

Unknowns / Needs Verification

None relevant to this release. The constituent dependency upgrades were individually merged and tested; this PR merely synthesizes those changes into a release tag. CI has already validated the full upgrade stack.