release: 0.5.70

[its-miso]

🤖 I have created a release beep boop

0.5.70 (2026-10-14)

Features

• deps: update dependency lucide-react (1.55.0 → 1.56.0) (#1241) (e50a0ee)
• deps: update dependency lucide-react (1.56.0 → 1.57.0) (#1258) (384ca59)
• lifecycle: persist idempotent claim and status transition evidence (#1202) (#1247) (bcae9a0)

Bug Fixes

• deps: update dependency @testing-library/user-event (14.6.7 → 14.6.8) (#1242) (caf1467)
• dockerfile: parse FROM --platform flag in splitIntoStages (#1178) (#1240) (a8fd35e)

Documentation

• observability: standalone portable observability design (#1237) (#1239) (941f426)

---

This PR was generated with Release Please. See documentation.

[its-saffron]

AI Automated Review

Full PR review.

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

Recommendation

Approve. No blocking or non-blocking defects were found in the release metadata changes.

Change-by-change assessment

• Release versions: .release-please-manifest.json, package.json, both root versions in package-lock.json, CHANGELOG.md, and both charts/dispatch/Chart.yaml version fields consistently identify 0.5.70.
• Release automation: release-please-config.json explicitly manages both Helm chart version fields, and the chart publication workflow verifies that the committed chart metadata matches the release tag.
• Runtime propagation: src/lib/version.ts resolves the displayed application version from package.json, so the package bump propagates through the repository's actual runtime consumer.
• Changelog: The included features, fixes, and documentation correspond to the commits between the prior release commit and this release head. CI-only changes are appropriately omitted.
• Helm dependency compatibility: This PR does not bump the chart dependency in Chart.lock; it remains on common 5.3.0, so no host/platform-coupled dependency compatibility matrix is implicated.

Required checks

• Breaking dependency APIs: Upstream release metadata describes Lucide 1.56.0 as icon additions/category metadata changes and user-event 14.6.8 as treating programmatic null input values as empty strings. Neither release identifies an API break.
• Full test suite: The exact head has successful Tests and Coverage runs, along with successful lint, typecheck, build, database, smoke, audit, and Docker checks.

Standards Compliance

The repository standard says lint and typecheck block CI and must pass; both are green on the exact head. The complete diff only changes release metadata and generated changelog content, so it neither introduces credentials nor modifies token logging, echoing, or persistence behavior.

Tool Harness Findings

Repository reads confirmed the Release Please configuration, package/manifest/chart version alignment, chart publication checks, runtime version consumer, CI gates, and dependency lock entries. Upstream release metadata was successfully fetched for both bundled dependency updates. The direct GitHub compare request and a read of the nonexistent path src/app/version.ts failed, but repository search located the actual implementation at src/lib/version.ts; neither failure leaves a mandatory check unresolved. The harness subsequently exhausted its tool budget.

Unknowns or Needs Verification

GitHub compare metadata for the target release range could not be retrieved. Local repository history independently establishes the bundled changes and their ordering, so this does not materially affect the verdict. No image digest changed in this PR.

Sources

• Repository release configuration and workflows: release-please-config.json, .github/workflows/release-please.yaml, .github/workflows/publish-chart.yaml
• Repository version consumers: package.json, package-lock.json, .release-please-manifest.json, charts/dispatch/Chart.yaml, src/lib/version.ts
• Exact-head CI results supplied in the review corpus
• Lucide 1.56.0 release: https://github.com/lucide-icons/lucide/releases/tag/1.56.0
• GitHub release metadata for Testing Library user-event 14.6.8