Skip to content

v0.97.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Jul 05:07
· 3851 commits to main since this release
v0.97.2
183c336

Important

v0.97.2 is a migration-safety hotfix. If v0.97.1 boots for you, you can upgrade at your leisure — nothing else changed. If your API crash-loops on upgrade with Migration checksum mismatch, this release is the fix.

Who is affected: self-hosters who ran v0.97.0 successfully against a superuser Postgres (the bundled docker-compose postgres role), then upgraded to v0.97.1. v0.97.1 rewrote 8 migration files in place (the non-superuser GUC fix), which is safe for anyone who skipped 0.97.0 as advised — but a database that had already applied the original 0.97.0 files recorded their old checksums, so the edited files trip the checksum guard on boot:

[CRITICAL] API startup failed: Error: Migration checksum mismatch for
2026-07-27-a-feature-policy-reference-ownership.sql. The file changed after being applied.

Deployments that went straight 0.96.0 → 0.97.1 (as the v0.97.1 note advised), and managed-Postgres/non-superuser deployments (where 0.97.0 never applied those files), were not affected.

Breeze RMM v0.97.2 — heal the v0.97.0 migration checksums so superuser self-hosters can upgrade past the crash-loop.

Fixed

  • Migration checksum mismatch crash-loop on upgrade — autoMigrate now recognizes the 8 migrations v0.97.1 rewrote in place (2026-07-27-a, -c, 2026-07-29, 2026-07-30, 2026-08-01-a/b/c/d) as a known, verified-safe forward-fix and heals the recorded checksum for any database that applied the original 0.97.0 versions, instead of refusing to boot. The heal only updates the breeze_migrations bookkeeping row — it never re-runs a migration — and the functions those databases already have are correct; the 0.97.1 rewrite only ever mattered for non-superuser fresh installs. Fresh installs and managed-Postgres deployments are untouched (#2627).

Self-Hosting / Upgrade Notes

No breaking changes. No new environment variables. No new migrations. This release is a single change to the migration checksum-reconciliation guard.

  1. Upgrade command. Bump BREEZE_VERSION=0.97.2, then docker compose pull api web && docker compose up -d (add pnpm install if you build from source).

  2. Database — nothing to apply. No new migrations. On boot, any database that was stuck on the checksum mismatch will log [auto-migrate] Reconciled checksum for <file> (known forward-fix: ...) for the affected files and then start normally. Databases that were already healthy see no change.

  3. No new required environment variables.

  4. No behavior changes or feature flags. This is a boot-path safety fix only; nothing in the running application changes from v0.97.1.

If you are currently crash-looping on v0.97.1, upgrading straight to v0.97.2 clears it — no manual database surgery required.

Full Changelog: v0.97.1...v0.97.2

Assets 33
Loading