container-runtime-policies.image was a sha256 digest from an older build, so every new local agent image built by a deploy went unused: tasks ran two-day-old agent code. Done when a deploy that builds the agent image makes new tasks run it (deploy updates the pin, or the dashboard shows the pinned image is not the newest build).
Close reason
archie-deploy --agent-image now runs archied update agent-image, so new tasks use the loaded build; verified a pinned digest is reset to :latest
Imported from beads archie-core-669jq · GitHub #1831 · type bug · priority P1 · created 2026-10-24 · closed 2026-10-24
container-runtime-policies.image was a sha256 digest from an older build, so every new local agent image built by a deploy went unused: tasks ran two-day-old agent code. Done when a deploy that builds the agent image makes new tasks run it (deploy updates the pin, or the dashboard shows the pinned image is not the newest build).
### Close reason
archie-deploy --agent-image now runs archied update agent-image, so new tasks use the loaded build; verified a pinned digest is reset to :latest
---
_Imported from beads `archie-core-669jq` · GitHub #1831 · type bug · priority P1 · created 2026-10-24 · closed 2026-10-24_
sam
added the highbug labels 2026-10-27 13:39:00 +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.
container-runtime-policies.image was a sha256 digest from an older build, so every new local agent image built by a deploy went unused: tasks ran two-day-old agent code. Done when a deploy that builds the agent image makes new tasks run it (deploy updates the pin, or the dashboard shows the pinned image is not the newest build).
Close reason
archie-deploy --agent-image now runs archied update agent-image, so new tasks use the loaded build; verified a pinned digest is reset to :latest
Imported from beads
archie-core-669jq· GitHub #1831 · type bug · priority P1 · created 2026-10-24 · closed 2026-10-24