docs: verify [Unreleased] against git since 1.2.5
test / test (push) Has been cancelled

Move restore Resync under Fixed to match e70ba90, and extend the restore
test bullet with the resync boot step and TestResyncAfterRestoreHealsDriftedMaps.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-08-14 19:30:12 +03:00
parent ba07decbb0
commit 74acf09212
+17 -15
View File
@@ -74,6 +74,14 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version
through a confirmation page, the same pattern as domain deletion, instead of through a confirmation page, the same pattern as domain deletion, instead of
a plain submit button next to Save with no confirmation at all. a plain submit button next to Save with no confirmation at all.
- panel (restore): after a backup is extracted and the version guard passes,
the panel runs one mail-path Resync on the first boot — OpenDKIM's tables
and Postfix's sender map are re-derived from SQLite and the daemons are
reloaded, so drift between the archive and the database is healed before
mail flows. Later starts skip that step; the Status page Reload button runs
the same Resync on demand. The `internal/backup` package comment now matches
this behaviour.
### Changed ### Changed
- docs: [guide.md](docs/guide.md) reorganised into **Installation**, **Instance - docs: [guide.md](docs/guide.md) reorganised into **Installation**, **Instance
@@ -125,13 +133,15 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version
downloaded from a running panel through `POST /backup` (plain and encrypted), downloaded from a running panel through `POST /backup` (plain and encrypted),
unpacked the way `tar -xzf` unpacks it onto the `/data` bind mount, and a unpacked the way `tar -xzf` unpacks it onto the `/data` bind mount, and a
second panel is booted on the result through the startup order the panel second panel is booted on the result through the startup order the panel
itself uses — version guard, database, services, HTTP application. The itself uses — version guard, database, one Resync when restoring, then
restored panel shows the domain and journal the archive carried, finds the services and the HTTP application. The restored panel shows the domain and
DKIM key, SASL database and Postfix sender map where its configuration says journal the archive carried, finds the DKIM key, SASL database and Postfix
they are, does not reopen the one-time setup link, and still honours a sender map where its configuration says they are, does not reopen the
session that predates the backup. A data directory left by another version is one-time setup link, and still honours a session that predates the backup.
refused with both versions named and the manifest kept. `serveHTTP` is split Drifted on-disk maps are healed by that Resync step
in two so that composition can be started without binding a port; no (`TestResyncAfterRestoreHealsDriftedMaps`). A data directory left by another
version is refused with both versions named and the manifest kept. `serveHTTP`
is split in two so that composition can be started without binding a port; no
behaviour change. behaviour change.
- test (e2e): the CoreDNS image is pinned to `1.14.6` instead of `latest`, so - test (e2e): the CoreDNS image is pinned to `1.14.6` instead of `latest`, so
@@ -188,14 +198,6 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version
longer promises in-panel report reception in a future release — SelfPost longer promises in-panel report reception in a future release — SelfPost
does not receive inbound mail. does not receive inbound mail.
- panel (restore): after a backup is extracted and the version guard passes,
the panel runs one mail-path Resync on the first boot — OpenDKIM's tables
and Postfix's sender map are re-derived from SQLite and the daemons are
reloaded, so drift between the archive and the database is healed before
mail flows. Later starts skip that step; the Status page Reload button runs
the same Resync on demand. The `internal/backup` package comment now matches
this behaviour.
## [1.2.5] - 2026-08-13 ## [1.2.5] - 2026-08-13
Rate-limit form polish after 1.2.4. Upgrading is a tag bump; no migration. Rate-limit form polish after 1.2.4. Upgrading is a tag bump; no migration.