Every untagged push to main republishes archied:latest with dev version stamping, so a release's stamping is transient #1371

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

Observed 2026-09-21, repeatedly, while landing ordinary commits.

WHAT HAPPENS
.github/workflows/deploy.yml's build-and-push job runs on any push to main OR to a release tag, and always pushes :latest. It resolves the version from the tags pointing at HEAD, and when there is no tag at HEAD it falls back to GATEWAY_VERSION=dev. So an ordinary commit pushed after a release rebuilds and republishes ghcr.io/samcharles93/archied:latest with a dev version string.

Concrete instance: archied/v1.34.0 was cut at 2ae831ab, and the very next commit (5adb1994, a docs-only architecture decision) immediately re-stamped :latest as dev. The same happened after v1.32.1 and v1.33.0.

WHY IT MATTERS

  • The version string is what an operator sees and what the update checker compares. A host that deploys :latest reports dev, so it reads as permanently behind every release and the update path cannot tell "current" from "stale".
  • The deploy workflow's own comment warns that images will be stamped dev, so this is known - but the consequence for the RELEASE is not: a release's stamping survives only until the next push to main, which in an active repo is minutes.
  • Note the runtime image is already protected from this: the archie-agent build step is skipped when there is no archie/v* tag at HEAD. Only archied is affected.

OPTIONS
(a) Publish :latest only from a tag, and have main pushes publish an immutable per-commit tag (e.g. :edge or :sha-) instead, so :latest always names the newest RELEASE.
(b) Keep publishing :latest from main but never fall back to dev - skip the version build-arg instead, or stamp :main as a distinct tag.
(a) is the conventional shape and makes :latest meaningful for a deploy; (b) is smaller but leaves :latest meaning "newest main" while its version string claims a release.

DECIDE BEFORE the next release, since the current behaviour silently degrades every release's artifact within minutes.

Close reason

Fixed in 36118f4e: :latest moves only from a release commit; other builds publish :edge.


Imported from beads archie-core-i5nb · GitHub #1107 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-26

Observed 2026-09-21, repeatedly, while landing ordinary commits. WHAT HAPPENS .github/workflows/deploy.yml's build-and-push job runs on any push to main OR to a release tag, and always pushes :latest. It resolves the version from the tags pointing at HEAD, and when there is no tag at HEAD it falls back to GATEWAY_VERSION=dev. So an ordinary commit pushed after a release rebuilds and republishes ghcr.io/samcharles93/archied:latest with a dev version string. Concrete instance: archied/v1.34.0 was cut at 2ae831ab, and the very next commit (5adb1994, a docs-only architecture decision) immediately re-stamped :latest as dev. The same happened after v1.32.1 and v1.33.0. WHY IT MATTERS - The version string is what an operator sees and what the update checker compares. A host that deploys :latest reports dev, so it reads as permanently behind every release and the update path cannot tell "current" from "stale". - The deploy workflow's own comment warns that images will be stamped dev, so this is known - but the consequence for the RELEASE is not: a release's stamping survives only until the next push to main, which in an active repo is minutes. - Note the runtime image is already protected from this: the archie-agent build step is skipped when there is no archie/v* tag at HEAD. Only archied is affected. OPTIONS (a) Publish :latest only from a tag, and have main pushes publish an immutable per-commit tag (e.g. :edge or :sha-<short>) instead, so :latest always names the newest RELEASE. (b) Keep publishing :latest from main but never fall back to dev - skip the version build-arg instead, or stamp :main as a distinct tag. (a) is the conventional shape and makes :latest meaningful for a deploy; (b) is smaller but leaves :latest meaning "newest main" while its version string claims a release. DECIDE BEFORE the next release, since the current behaviour silently degrades every release's artifact within minutes. ### Close reason Fixed in 36118f4e: :latest moves only from a release commit; other builds publish :edge. --- _Imported from beads `archie-core-i5nb` · GitHub #1107 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-26_
sam added the mediumbug labels 2026-10-27 13:40:07 +00:00
sam self-assigned this 2026-10-27 13:40:07 +00:00
sam closed this issue 2026-10-27 13:40:07 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1371