release: 0.5.71

[its-miso]

🤖 I have created a release beep boop

0.5.71 (2026-10-16)

Features

• deps: update dependency astro (5.18.2 → 7.4.0) (#1281) (f548ef8)
• deps: update dependency eslint (10.12.0 → 10.13.0) (#1288) (89b6f22)
• deps: update dependency lucide-react (1.57.0 → 1.58.0) (#1284) (a5f3305)
• pr-fix: persist authoritative evidence versions and attempt-snapshot freshness (#1249) (#1276) (d292094)
• pr-fix: structured external-wait dependency contract and fail-closed holds (#1273) (ef4feaa)

Bug Fixes

• api: reject status transitions on closed issues in POST /api/issues/status (#1285) (d4e532a), closes #1206
• ci: isolate external-wait queue assertions (#1283) (c2ea489)
• deps: update dependency @prisma/adapter-pg (7.10.0 → 7.10.1) (#1267) (8f7284c)
• deps: update dependency @prisma/client (7.10.0 → 7.10.1) (#1268) (24ee983)
• deps: update dependency jsdom (30.1.2 → 30.1.3) (#1264) (f8d8537)
• deps: update dependency prisma (7.10.0 → 7.10.1) (#1269) (270ac1a)
• deps: update nextjs monorepo (16.4.1 → 16.4.2) (#1272) (4132528)
• deps: update vitest monorepo (5.0.4 → 5.0.5) (#1265) (0021632)
• test: pin PR-fix comment footer clock and drop brittle 99 guard (#1257) (#1271) (572d2fa)
• webhook: guard issue-label cache writes with compare-and-swap (#1220) (#1266) (1b4b976)

Chores

• ci: disable experimental requirement tracing (#1289) (c50c838)

Documentation

• recovery: design PR-fix reactivation on fresh evidence (#1244) (#1248) (bce947c)

---

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.1-Flash-Preview (anthropic) — primary route · pr-reviewer-action v3.5.0

Recommendation

Approve. This is a release-preparation change that consistently advances the root package, lockfile, release manifest, changelog, and Helm chart to 0.5.71. No locatable release-metadata defect was found, and the exact head passed the full relevant CI suite.

Change Review

• Release metadata — held: the release-please manifest, package manifest, both root package-lock version fields, chart version, chart appVersion, and changelog heading consistently identify 0.5.71.
• Previous-version references — held: the remaining 0.5.70 occurrences are correctly confined to the new comparison URL and the preceding changelog section.
• Application version propagation — held: src/lib/version.ts obtains the application version from package.json or the build-time environment, so this manifest update feeds the existing version-label path without another hardcoded change.
• Helm behavior — held: chart metadata advances both fields, and the chart templates still fall back to appVersion when no image tag is supplied.
• Dependency/API compatibility check — held: this diff does not alter dependency resolution or application APIs; it only packages the constituent merged changes into release metadata. Repository history confirms the listed dependency updates are already preceding commits, and the exact release head passed build, lint, typecheck, integration, smoke, Docker, and audit checks.
• Closed-issue status claim — held: the endpoint contains a closed-state rejection before writes, and the corpus includes tests for both the no-write path and rejection before the live-label assignment gate.
• Evidence version/snapshot claim — held by available evidence: the repository contains targeted ledger and settlement tests, including watermark-race and archived-attempt snapshot coverage, and the complete test job passed at this head.
• External-wait fail-closed claim — unverified: the repository contains external-wait tests and the full suite passed, but the supplied corpus does not expose the individual missing/malformed/pending/failed/satisfied assertions needed to independently verify every state in that claim. This is not a release-metadata defect and does not withhold approval.

Standards Compliance

The release update follows the repository conventions: lint and typecheck are blocking CI checks, and both passed. The changed files introduce no token handling, logging, echo, or persistence behavior; no secrets are added by this release-only diff.

Tool Harness Findings

Repository searches found 0.5.71 in every expected release-version location and no stale 0.5.70 references outside legitimate changelog comparison/history text. Inspection confirmed that release-please-config.json explicitly manages both Helm metadata fields, src/lib/version.ts consumes the package/build version dynamically, and the unrelated site package intentionally remains at its own 0.1.0 version. Repository history shows the release commit immediately follows the constituent fixes and dependency updates listed in the changelog. Search results also located the closed-issue rejection and its regression tests.

Sources

• .release-please-manifest.json
• package.json
• package-lock.json
• charts/dispatch/Chart.yaml
• release-please-config.json
• src/lib/version.ts
• src/app/api/issues/status/route.ts
• Exact-head CI results for commit 38d5c43
• Release comparison: upstream misospace/dispatch compare v0.5.70...v0.5.71

Unknowns or Needs Verification

• The linked issue bodies were unavailable, so their detailed acceptance criteria could not be compared directly.
• The external-wait claim's complete state matrix was not exposed by the supplied repository evidence; no failing counterexample was observed.