From 3b8ac7cb1c0de458d5bb170e11d59784193a9801 Mon Sep 17 00:00:00 2001 From: archipelago Date: Mon, 3 Aug 2026 08:58:43 -0400 Subject: [PATCH] docs(state): v1.7.120-alpha shipped and verified live Records the two release-process traps for the next cut: the manifest is committed before signing (so the fleet would refuse the OTA), and gitea-vps2 is the same server as gitea-ai with a dead token. Co-Authored-By: Claude Opus 5 (1M context) --- .planning/STATE.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.planning/STATE.md b/.planning/STATE.md index 13c32995..5bb0030d 100644 --- a/.planning/STATE.md +++ b/.planning/STATE.md @@ -164,7 +164,14 @@ Decisions are logged in PROJECT.md (10 locked ADRs in the `` block + | Fleet | FLEET-02 per-app deep health assertions (~34 apps) | v2 | 2026-07-29 | | Fleet | FLEET-03 LUKS2 data-partition encryption | v2 | 2026-07-29 | -## Release staging — v1.7.120-alpha (2026-08-03) +## Release SHIPPED — v1.7.120-alpha (2026-08-03) + +**LIVE.** signature PRESENT (did:key:z6Mkkid…q7ur), both assets HTTP 200 at exactly their +manifest byte counts, tag pushed. Two release-process traps hit and documented in memory: +create-release.sh commits the manifest BEFORE signing (fleet refuses unsigned), and +gitea-vps2 is the SAME server as gitea-ai (vps2 token is dead). + +### Staging record (kept for the evidence trail) Built from `4d67f56b` (release profile, 15m15s, exit 0), deployed to archi-dev-box, `.bak` rollback at /opt/archipelago/rollback/archipelago.bak.