scripts/archie-update-install builds and installs only ./cmd/archied (lines 148-158). The documented production deployment (deployments/systemd-user-service.md) runs four user units: archied.service, archie-gateway.service, archie-state-store.service, archie-ui.service. The updater never builds or installs archie-gateway, archie-state-store, archie-ui or archie-playbooks.
scripts/archie-update-watchdog:107 compounds it: it restarts only archied.service, so even the binaries it does not replace are never restarted.
This became deployment-breaking at 1.23.0, the release that made those processes mandatory. internal/app/archied/bootstrap.go:330 hard-fails archied when services.state.target is unreachable. A self-update to 1.23.0 installs a new archied against a 1.22.0-era or absent State Store, Gateway and UI.
Design questions to settle before coding: whether all four binaries version together off the archied tag; restart ordering (state store must be up before archied); health verification per unit; and rollback semantics when one of four installs fails.
Acceptance criteria
A self-update to a release installs every binary the documented deployment runs, restarts their units in a safe order, verifies health, and rolls all of them back together on failure.
Close reason
Closed
Imported from beads archie-core-hbqk · GitHub #795 · type bug · priority P0 · created 2026-09-11 · closed 2026-09-11
scripts/archie-update-install builds and installs only ./cmd/archied (lines 148-158). The documented production deployment (deployments/systemd-user-service.md) runs four user units: archied.service, archie-gateway.service, archie-state-store.service, archie-ui.service. The updater never builds or installs archie-gateway, archie-state-store, archie-ui or archie-playbooks.
scripts/archie-update-watchdog:107 compounds it: it restarts only archied.service, so even the binaries it does not replace are never restarted.
This became deployment-breaking at 1.23.0, the release that made those processes mandatory. internal/app/archied/bootstrap.go:330 hard-fails archied when services.state.target is unreachable. A self-update to 1.23.0 installs a new archied against a 1.22.0-era or absent State Store, Gateway and UI.
Design questions to settle before coding: whether all four binaries version together off the archied tag; restart ordering (state store must be up before archied); health verification per unit; and rollback semantics when one of four installs fails.
### Acceptance criteria
A self-update to a release installs every binary the documented deployment runs, restarts their units in a safe order, verifies health, and rolls all of them back together on failure.
### Close reason
Closed
---
_Imported from beads `archie-core-hbqk` · GitHub #795 · type bug · priority P0 · created 2026-09-11 · closed 2026-09-11_
sam
added the criticalbug labels 2026-10-27 13:40:04 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
scripts/archie-update-install builds and installs only ./cmd/archied (lines 148-158). The documented production deployment (deployments/systemd-user-service.md) runs four user units: archied.service, archie-gateway.service, archie-state-store.service, archie-ui.service. The updater never builds or installs archie-gateway, archie-state-store, archie-ui or archie-playbooks.
scripts/archie-update-watchdog:107 compounds it: it restarts only archied.service, so even the binaries it does not replace are never restarted.
This became deployment-breaking at 1.23.0, the release that made those processes mandatory. internal/app/archied/bootstrap.go:330 hard-fails archied when services.state.target is unreachable. A self-update to 1.23.0 installs a new archied against a 1.22.0-era or absent State Store, Gateway and UI.
Design questions to settle before coding: whether all four binaries version together off the archied tag; restart ordering (state store must be up before archied); health verification per unit; and rollback semantics when one of four installs fails.
Acceptance criteria
A self-update to a release installs every binary the documented deployment runs, restarts their units in a safe order, verifies health, and rolls all of them back together on failure.
Close reason
Closed
Imported from beads
archie-core-hbqk· GitHub #795 · type bug · priority P0 · created 2026-09-11 · closed 2026-09-11