ci: retire publish-agent-image.yml, folded into the unified release lane (RIG-2994) - #756
Merged
mattwilkinsonn merged 3 commits intoAug 30, 2026
Conversation
…ane (RIG-2994) T4 of the unified-release-lane design (RIG-1746, DL-300): the standalone per-push GHCR publish workflow retires now that its duty runs in the unified release.yml `publish-image` job. - Delete `.github/workflows/publish-agent-image.yml`. The per-push `:git-<sha12>` + `:latest` publish duty (verbatim `agent-image/publish.sh`, same closure-paths gate, same serialize / immutability / two-copy-coherence / least-privilege / off-hot-path posture) now lives in the unified lane's `publish-image` job on RigelBuild/compass main. - Update the superseded-in-part note on `docs/designs/infra/ci/compass-agent-image-publish/design.md` to record the retirement as done (the RIG-1746 note already prescribed the two-PR staged delete; this completes it). Every other decision in that record — the `:git-<sha>` immutable tag contract, the build-once/push-each-tag skopeo mechanism, the auth pin, the linux/amd64 platform contract, the public-visibility ruling — stays live and is carried into the unified lane; the record remains the cited authority for the baked `:git-<sha>` pin. Two-PR staging satisfied before this delete: RIG-2914/2915/2916 landed release.yml on main (#743 mergeCommit 867159a), and three green per-push `publish-image` runs were observed on real main pushes (5219558 8m1s, 7eddb90 9m37s, 7188de6 8m20s) — the relocated duty is proven end-to-end. Per-push GHCR consumers (ci.yml dogfood DL-112, app-bundle SMOKE.md, the baked :git-<sha> pin) consume the published tags, which the unified lane still produces, so they are unaffected by removing the workflow file. Ledger-impact: none — the CI-placement supersession was already recorded by RIG-1746 (DL-298–301); this PR completes the prescribed file retirement and carries no new ledger decision. Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
Compass engineering docs preview: https://compass-managed-rig-2994-ret.compass-eng-docs.pages.dev Deployed from Changed pages: |
…-2994) Review low on #756: the architecture doc still framed the standalone workflow retirement as a pending follow-up. It has happened in this PR, so update the prose to past tense (the file is retired, its per-push publish duty relocated into release.yml publish-image). Ledger-impact: none — doc-accuracy tense fix, no design decision. Co-authored-by: Matt Wilkinson <matt@rigel.build>
Two live-surface comments still named the deleted workflow. Retarget them to the current source of truth so nothing dangles after the file retires: - ci.yml image-affected detector: the closure source of truth is now release.yml IMAGE_CLOSURE_PATHS, not publish-agent-image.yml on.push.paths. - tools/release-notes: the GHCR repo + digest-query citations point at release.yml's publish-image job, not the deleted file's line numbers. Comment-only; release-notes tests 22 pass. Frozen docs/designs/** citations are historical (pinned HEAD) and intentionally left. Ledger-impact: none — comment retargeting, no design decision. Co-authored-by: Matt Wilkinson <matt@rigel.build>
mattwilkinsonn
marked this pull request as ready for review
August 30, 2026 22:25
mattwilkinsonn
approved these changes
Aug 30, 2026
mattwilkinsonn
deleted the
compass-managed/rig-2994-retire-publish-agent-image
branch
August 30, 2026 22:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
T4 of the unified-release-lane design (RIG-1746, DL-300): the standalone
per-push GHCR publish workflow retires now that its duty runs in the unified
release.yml
publish-imagejob..github/workflows/publish-agent-image.yml. The per-push:git-<sha12>+:latestpublish duty (verbatimagent-image/publish.sh,same closure-paths gate, same serialize / immutability / two-copy-coherence /
least-privilege / off-hot-path posture) now lives in the unified lane's
publish-imagejob on RigelBuild/compass main.docs/designs/infra/ci/compass-agent-image-publish/design.mdto record theretirement as done (the RIG-1746 note already prescribed the two-PR staged
delete; this completes it). Every other decision in that record — the
:git-<sha>immutable tag contract, the build-once/push-each-tag skopeomechanism, the auth pin, the linux/amd64 platform contract, the
public-visibility ruling — stays live and is carried into the unified lane;
the record remains the cited authority for the baked
:git-<sha>pin.Two-PR staging satisfied before this delete: RIG-2914/2915/2916 landed
release.yml on main (#743 mergeCommit 867159a), and three green per-push
publish-imageruns were observed on real main pushes (5219558 8m1s,7eddb90 9m37s, 7188de6 8m20s) — the relocated duty is proven end-to-end.
Per-push GHCR consumers (ci.yml dogfood DL-112, app-bundle SMOKE.md, the baked
:git- pin) consume the published tags, which the unified lane still
produces, so they are unaffected by removing the workflow file.
Ledger-impact: none — the CI-placement supersession was already recorded by
RIG-1746 (DL-298–301); this PR completes the prescribed file retirement and
carries no new ledger decision.
Co-authored-by: Matt Wilkinson matt@rigel.build