Repository navigation
feat: publish images to GHCR and release from release branches - #2
Merged
Merged
Conversation
ykhrustalev
force-pushed
the
ykhrustalev/publish-multi-arch-images-to-ghcr
branch
4 times, most recently
from
August 11, 2026 00:20
1394c70 to
906e7c8
Compare
ykhrustalev
force-pushed
the
ykhrustalev/publish-multi-arch-images-to-ghcr
branch
5 times, most recently
from
August 11, 2026 01:36
ce92e9b to
fdda356
Compare
The Docker job built both architectures and discarded them, so nothing this repository produces was consumable. GHCR needs no configured secret, authenticating with the job-scoped GITHUB_TOKEN. A pull request builds both architectures to prove the Dockerfile still works but pushes nothing: main exercises the publish path on every merge, so repeating it per pull request only leaves package versions behind that nobody cleans up. Main pushes the image; a push to release/** pushes it and cuts a GitHub release. The version is the train from the branch name, the distance from the branch point and the commit — 2026.08.1-3-ga1b2c3d4ab. It reads no clock and needs no pre-existing tag, so a commit always names itself the same way, and the tag the release creates can never move because the sha is part of it. The naming lives in ci/version.sh so it can be run locally to answer what a commit would publish as, rather than only inside a workflow.
ykhrustalev
force-pushed
the
ykhrustalev/publish-multi-arch-images-to-ghcr
branch
from
August 11, 2026 01:56
fdda356 to
cbc241d
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.
Problem
docker-image-buildbuilt both architectures and discarded them (outputs: type=cacheonly), so nothing this repository produces was consumable. GHCR needs no configured secret — it authenticates with the job-scopedGITHUB_TOKEN— and this repository has none.Solution
docker-image-publishrelease/**pushes it and cuts a GitHub release2026.08.1-3-ga1b2c3d4ab— train, distance from the branch point, commit. No clock and no pre-existing tag, so a commit always names itself the same wayci/version.sh, runnable locally to answer what a commit would publish asTesting
ghcr.io/liquid4all/pipette-scores:pr-2published as alinux/amd64+linux/arm64manifest before pull-request pushing was turned off, confirming the publish path end to endci/version.shexercised across main, a fresh release branch, a release branch three commits in, after main moves, after merging main back, and a second concurrent train