R-85 Phase 4: finalise v0.104.0 + register the new helpers in REUSE
Version finalised from v0.104.0-dev — an ldflags version disagreeing with the CHANGELOG is the reconciliation problem hub 0.73.2 already caused. REUSE gains backup.InFlight, backup.RestoreTestState and the SpecBuilder/ TierPicker/PickRestoreCandidateOn trio, each with the decision someone could unknowingly undo: rotation credit only on success; InFlight callers defer and never cancel; a tier with no archive no-ops rather than failing; SourceTier comes from the archive, never the configured target.
This commit is contained in:
+2
-2
@@ -1,4 +1,4 @@
|
||||
## v0.104.0-dev — R-85 Phase 2: tier rotation, persisted state, one heavy op at a time (2026-07-26)
|
||||
## v0.104.0 — R-85: unattended per-tier restore-test (Phase 2): tier rotation, persisted state, one heavy op at a time (2026-07-26)
|
||||
|
||||
The scheduler could only ever see `cfg.Backup.BackupTarget()`, so the offsite tier's archives were
|
||||
never candidates. That is why demo-hp's DR tier reported `applied` with **zero snapshots for five
|
||||
@@ -46,7 +46,7 @@ otherwise a permanently broken tier would look freshly proven and quietly stop b
|
||||
|
||||
Full suite green (29 packages, `rc=0`, vet unpiped).
|
||||
|
||||
## v0.104.0-dev — R-85 Phase 1: the restore-test spec is built PER RUN (2026-07-26)
|
||||
## v0.104.0 (cont.) — R-85 Phase 1: the restore-test spec is built PER RUN (2026-07-26)
|
||||
|
||||
Prerequisite for scheduling the offsite tier at all. Shipped on its own because it is independently
|
||||
correct and independently testable.
|
||||
|
||||
Reference in New Issue
Block a user