Channel, digest pinning, and in-flight-safe auto-update #286

Closed
opened 2026-10-27 13:35:42 +00:00 by sam · 0 comments
Owner

Design: docs/prds/self-update-transaction.md#channel-pinning-automation-804-item-4. Adds ReleaseChannel (stable|next|exact-pin) distinct from the existing chat-notification channel field at internal/releaseupdate/command.go:62; Catalog.Check filters by it. Every shipped deployment profile already pins images by digest (confirmed) -- the remaining gap is archie-update-install falling back to :latest when no digest is configured; it must resolve the profile's digest or refuse, never pull :latest silently. Opt-in auto-update refuses to start when the daemon reports work in flight (reuse the existing drain/shutdown in-flight signal, no second tracker).

Acceptance criteria

Channel filtering logic is pure and covered by task check. archie-update-install has a fixture test proving it refuses rather than falling back to :latest when no digest resolves. Auto-update path has a test proving it refuses to start with tasks in flight.

Notes

Suggested council lens: lens-contract (digest-refusal changes what a config value is allowed to resolve to).

Close reason

Closed


Imported from beads archie-core-hj1t.4 · GitHub #931 · type task · priority P2 · created 2026-09-19 · closed 2026-10-05

Design: docs/prds/self-update-transaction.md#channel-pinning-automation-804-item-4. Adds ReleaseChannel (stable|next|exact-pin) distinct from the existing chat-notification channel field at internal/releaseupdate/command.go:62; Catalog.Check filters by it. Every shipped deployment profile already pins images by digest (confirmed) -- the remaining gap is archie-update-install falling back to :latest when no digest is configured; it must resolve the profile's digest or refuse, never pull :latest silently. Opt-in auto-update refuses to start when the daemon reports work in flight (reuse the existing drain/shutdown in-flight signal, no second tracker). ### Acceptance criteria Channel filtering logic is pure and covered by task check. archie-update-install has a fixture test proving it refuses rather than falling back to :latest when no digest resolves. Auto-update path has a test proving it refuses to start with tasks in flight. ### Notes Suggested council lens: lens-contract (digest-refusal changes what a config value is allowed to resolve to). ### Close reason Closed --- _Imported from beads `archie-core-hj1t.4` · GitHub #931 · type task · priority P2 · created 2026-09-19 · closed 2026-10-05_
sam added the mediumepictask labels 2026-10-27 13:35:42 +00:00
sam self-assigned this 2026-10-27 13:35:42 +00:00
sam closed this issue 2026-10-27 13:35:42 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#286