From f7f3cc4ee2b193353070086a019482c87e202cb4 Mon Sep 17 00:00:00 2001 From: Wynne Pirini Date: Thu, 19 Nov 2026 11:35:02 +1300 Subject: [PATCH] docs(changelog): require a database backup before the payments migration The unreleased work includes migration 00072, which renames two columns on `bookings` and adds `payment_provider`. Migrations run automatically at boot, so an operator only learns about it when the app starts the new image. Records it in the `[Unreleased]` section, which is what becomes the release body, so the instruction cannot be missed at the one moment it matters. Covers both deployment paths: the Litestream drill for Docker and Railway (including the `calnode.key` caveat, since the replica holds the database and not the key), and a module backup for NS8, which captures the volume and `state/calnode.env` where the key lives. No code change. --- CHANGELOG.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index bcc97b0f..6eec3898 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,25 @@ exact tag (`ghcr.io/calnode/calnode:0.1.0`) if you need stability between upgrad ## [Unreleased] +### Upgrading + +- **Back up the database before upgrading.** This release includes a migration (`00072`) + that renames two columns on `bookings` and adds one. Migrations run automatically at + boot, so the upgrade is the moment to want a restore point that predates it. + + - **Docker or Railway.** Take the backup deliberately rather than assuming a replica + exists somewhere, and prove it restores while the app is still on the old version: the + non-destructive drill in `DEPLOY.md` ยง6 restores to a scratch path without touching the + live database. If you run without `CALNODE_ENCRYPTION_KEY`, also copy + `/data/calnode.key`. The replica holds the database, not the key, and a restore without + it will not start. + - **NS8 module.** Run a module backup before pulling the new image. It captures + `volumes/calnode-data` and `state/calnode.env`, which is where the encryption key lives. + + The migration has a down path that restores both column names and keeps the data, but a + backup is the only safety net for anything that goes wrong between the migration running + and your first check that existing bookings still look right. + ### Added - **German without du or Sie (`de-x-neutral`).** An opt-in wording variant of the German