Files
felhom-agent/REPORT.md
T
admin 24ea960229
gates / gates (push) Successful in 1m7s
REPORT: v0.154.0 released and delivered (2026-10-09)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-09 08:36:51 +02:00

1.4 KiB
Raw Blame History

REPORT — v0.154.0 released and delivered (2026-10-09)

Built from the 2026-10-09 kernel-night read-back: (1) the host report now adds the saved newest backup success per tier (R-894's file, one shared instance), so a restart right after a night backup no longer empties the hub's evidence — on demo-felhom it had caused a false „newest backup is 48h old" alarm; (2) proxmox-secure-boot-support joins the boot-chain lane, so it no longer pulls shim-signed-common into the ring-0 Proxmox plan (demo-hp's step was refused R6 and its kernel step skipped). Red-proofs: TestCollectBackups_SavedSuccessSurvivesARestart, TestR894_LastKnownBackupsIsWiredIntoTheDaemon, test_ring0_pending_pve_leaves_the_secure_boot_meta_out.

scripts/release-agent.sh 0.154.0: sha 36a54ad2…, bundle 93487989…, tag v0.154.0 = db25b46, verified by download. CI 1576 (code) success; 1579 (CHANGELOG) failed in its fetch step (Gitea answered 500), re-run → success. Signed agent_update → demo-hp, demo-felhom, Tester 1 (07:16–07:18 local); signed agent_config_update → BUNDLE DONE written=1 same=26 self-check=ok, capability probe 68/68 on all three. NOT vouched (the vouch needs a golden at or above the fleet's controller; no golden today). Live: demo-felhom's first report after the update carries the 02:40Z backup. Evidence: felhom.eu/documentation/audits/release-2026-10-09/delivery/.