Repository navigation
ci: publish multi-arch images to GHCR - #1
Closed
ykhrustalev wants to merge 3 commits into
Closed
ykhrustalev wants to merge 3 commits into
ykhrustalev wants to merge 3 commits into
Conversation
The Docker job built both arches and threw them away (`type=cacheonly`), so nothing this repository produces was consumable. Publish to GHCR instead: it authenticates with the job-scoped GITHUB_TOKEN, so it needs no configured secret — this repo has none. Each arch pushes a digest with no tag, and a new docker-image-publish job joins the digests into one manifest list and applies the tags. Tagging per-arch in the matrix would have the two runners race, each overwriting the other's tag with a single-arch image. Tags follow the ref: `pr-<n>` on a pull request, `main` plus the date+sha version on main, and the train number on release/** (release/2026.08.1 -> 2026.08.1). The image path is lowercased because GHCR rejects uppercase segments and the org is `Liquid4All`. The pull_request base filter gains release/** too, so a fix cherry-picked onto a release train still gets CI before it lands. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Taking the version from the branch name pinned every push to a release branch at the same string, so a second push could not produce a new release. `git describe` bumps on its own instead: 2026.08.1 -> 2026.08.1-1-g<sha> -> 2026.08.1-2-g<sha> -> ... Each push is a distinct version, so nothing has to move a tag. `git describe` needs the tags and the history behind them, which the default shallow checkout fetches neither of, so release-metadata now checks out with fetch-depth: 0. These repositories carry no tags at all today (they were squashed), and bare `git describe` fails outright with "No tags can describe" rather than degrading, so an unreachable-tag fallback keeps the date+sha scheme the repo has always used until a release train is tagged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Each tag contributes two entries to TAG_ARGS (`-t` and the ref), so the message reported "2 tag(s)" for the single pr-1 tag. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ykhrustalev
force-pushed
the
ci/ghcr-publish
branch
from
August 10, 2026 23:12
b86c269 to
ed83491
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.
Why
docker-image-buildbuilt both arches and discarded them (outputs: type=cacheonly, commented "Build only. Neverpush=true, on any branch or event"), so nothing this repository produces was consumable anywhere.GHCR rather than Docker Hub because it authenticates with the job-scoped
GITHUB_TOKENand needs no configured secret. This repo currently has zero secrets and zero variables.Note this publishes the image, not a wheel —
wheel-smokestill builds its wheel purely to prove the bundled IFBench import works and does not persist it. Nothing in this PR changes that.What changed
docker-image-buildlogs intoghcr.ioand pushes a digest only, no tag, per archdocker-image-publishjob joins the per-arch digests into one multi-arch manifest list and applies the tags, then inspects the result so a broken manifest fails in CI rather than at pull timeon.pushgainsrelease/**, and thepull_requestbase filter gains it too so a fix cherry-picked onto a release train still gets CITagging inside the matrix instead would have the amd64 and arm64 runners race, each overwriting the other's tag with a single-arch image — hence the split.
Tags
ghcr.io/liquid4all/pipette-scorespr-<n>main,<date>-<sha>release/2026.08.12026.08.1The image path is lowercased in
release-metadata— GHCR rejects uppercase path segments and the org isLiquid4All, sogithub.repositorycannot be used verbatim.Verifying
This PR exercises the full push path and should publish
ghcr.io/liquid4all/pipette-scores:pr-<n>as a two-arch manifest.Worth watching on the first run: this creates the GHCR package for the first time. If the org disallows
GITHUB_TOKENcreating org packages, the push fails withdenied: installation not allowed to Create organization packageand needs a one-time org setting — that is exactly what this PR is meant to surface before a release depends on it.The
pr-<n>tag is disposable and can be pruned after review.There is no
build-completeaggregate gate in this repo, sodocker-image-publishappears as its own required-check candidate if you gate on it.The
release/**trigger is inert until such a branch exists.🤖 Generated with Claude Code