Repository navigation
ci: test container builds and gate deployment tags - #2
Merged
Merged
Conversation
robjtede
force-pushed
the
t3/auto-docker-stable-promotion
branch
from
October 8, 2026 23:40
91d5a2c to
a4efd5b
Compare
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
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.
PRs now build and smoke-test the AMD64 container image without publishing. The container workflow keeps the reusable CI and published-digest smoke test already on main.
Each push to
mainpublishes a full-SHA candidate. After formatting, Clippy, tests, the image build, and the published-image smoke test pass,stableandlatestmove to the candidate digest without rebuilding it. Manual runs can publish and promote only frommain.Validation:
just container-smokepassed against the existing local ARM64 image.