Gateway-only release must not rebuild or publish archie-agent #1637

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

Bug Description

A gateway-only release (archied v1.22.0, runtime skipped) still runs the Build and push archie-agent job and pushes ghcr.io/samcharles93/archie-agent:latest with RUNTIME_VERSION=dev because no archie/v1.22.0 tag exists. This violates the release process rule that an untouched component must not be rebuilt or published.

Evidence

  • Release target: archied/v1.22.0 only; archie-agent was explicitly skipped.
  • Workflow: .github/workflows/deploy.yml unconditionally builds both images.
  • Version resolver uses RUNTIME_VERSION=dev when no runtime tag points at HEAD.
  • Tag workflow 33723604418 passed, but rebuilt/pushed the agent image anyway.

Expected Behavior

A gateway-only release builds and publishes only the archied component. The existing agent image remains unchanged.

Acceptance Criteria

  • Make the deploy workflow component-aware: skip the agent build/push when no archie/v* release tag points at HEAD.
  • Preserve full dual-image builds when both component tags are present.
  • Add CI/workflow validation for gateway-only and dual-component releases.
  • Do not publish an agent image stamped dev from a gateway-only release.

Close reason

Resolved by commit 5f2b253 (PR #712); GitHub #710 closed. Stale-open copy recovered from carina during machine sync.


Imported from beads archie-core-w1d5 · GitHub #710 · type bug · priority P1 · created 2026-09-03 · closed 2026-09-03

## Bug Description A gateway-only release (`archied v1.22.0`, runtime skipped) still runs the `Build and push archie-agent` job and pushes `ghcr.io/samcharles93/archie-agent:latest` with `RUNTIME_VERSION=dev` because no `archie/v1.22.0` tag exists. This violates the release process rule that an untouched component must not be rebuilt or published. ## Evidence - Release target: `archied/v1.22.0` only; `archie-agent` was explicitly skipped. - Workflow: `.github/workflows/deploy.yml` unconditionally builds both images. - Version resolver uses `RUNTIME_VERSION=dev` when no runtime tag points at HEAD. - Tag workflow 33723604418 passed, but rebuilt/pushed the agent image anyway. ## Expected Behavior A gateway-only release builds and publishes only the archied component. The existing agent image remains unchanged. ## Acceptance Criteria - Make the deploy workflow component-aware: skip the agent build/push when no `archie/v*` release tag points at HEAD. - Preserve full dual-image builds when both component tags are present. - Add CI/workflow validation for gateway-only and dual-component releases. - Do not publish an agent image stamped `dev` from a gateway-only release. ### Close reason Resolved by commit 5f2b253 (PR #712); GitHub #710 closed. Stale-open copy recovered from carina during machine sync. --- _Imported from beads `archie-core-w1d5` · GitHub #710 · type bug · priority P1 · created 2026-09-03 · closed 2026-09-03_
sam added the highbug labels 2026-10-27 13:41:11 +00:00
sam self-assigned this 2026-10-27 13:41:11 +00:00
sam closed this issue 2026-10-27 13:41:11 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1637