v0.53.1: refresh recovery units on periodic cache cycle (idempotent)
CaptureRecoveryUnit now builds content in memory and skips writes when the unit is already current (checksum + dump-set + version), so it can run from RefreshCache (startup + every 5m) without thrashing the USB drive. Units now exist shortly after startup and track config changes without waiting for the daily DB dump. +idempotency test. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -1,5 +1,14 @@
|
||||
## Changelog
|
||||
|
||||
### v0.53.1 — Phase 2: recovery units refresh on the periodic cache cycle (idempotent) (2026-06-13)
|
||||
|
||||
The recovery-unit capture now also runs from `RefreshCache` (controller startup + every 5m), not only
|
||||
the daily DB dump — so a unit exists shortly after startup and stays current with config changes
|
||||
(redeploy / optional-config) without a 24h wait. `CaptureRecoveryUnit` builds the captured content in
|
||||
memory and **skips all writes when the unit is already current** (same config checksums + dump set +
|
||||
controller version), so the periodic refresh does not thrash a spinning USB drive. Added an idempotency
|
||||
test (unchanged → skip; config change → rewrite).
|
||||
|
||||
### v0.53.0 — Phase 2: per-app self-contained recovery unit (capture side, SECRET-FREE) (2026-06-13)
|
||||
|
||||
Each app's on-drive backup becomes a complete, recreatable **recovery unit** — not just DB dumps +
|
||||
|
||||
Reference in New Issue
Block a user