Files
esh-pfi-infrastructure/persistent-memory.d/2026-09-19-althing-3-7-0-rolled-out-to-both-infra-ops-surfaces-and-the.md
T

1.2 KiB

[2026-09-19] althing 3.7.0 rolled out to both infra-ops surfaces — and the rollout broke the claim tooling built that morning.

⭐⭐ althing 3.7.0 rolled out to both infra-ops surfaces — and the rollout broke the claim tooling built that morning. Post office on nh3-docker (built from althing@6db955f, manifest sha256:df0709b3, 10.9 s recreate, volume preserved) and the nh3-extdev system wheel + herald. forseti independently verified both. ⚠ Everything CONTENT-verified, never tag-verified: postbox --version inside the image before the push and inside the running container after; data continuity proven by reading forseti's own message back out of the running 3.7.0 store. ⚠ deploy-stack.sh rsyncs with --delete, so the host-side .bak-<version> compose convention is GONE — it converges rather than accretes; rollback is git history + the retained 3.6.3 registry digest. ⚠ The claim bug: a 45-minute operation claim was refreshed and then released by deploy-stack.sh's exit trap, silently dropping the protection mid-rollout. Fixed 3e7d3a3 — ops-log claim exits 10 when the claim is already the caller's and leaves the holder file UNTOUCHED (a refresh would overwrite the reason and TTL the original claimant chose).