ci: also publish to legacy py-baleen-cpu / py-baleen-gpu Docker Hub repos#5
Merged
Conversation
…ub repos
Before the single-repo switch, images lived in separate Docker Hub repos
btrspg/py-baleen-cpu and btrspg/py-baleen-gpu; those still hold stale f5c-era
images that users/scripts may pull. Keep them in sync by pushing each build to
the legacy repo as well, alongside the new single py-baleen repo.
Each build job now runs two metadata steps:
- meta: ${DH_USER}/py-baleen + ghcr.io/<owner>/py-baleen, variant as a
tag suffix (-cpu/-gpu), explicit per-tag-suffixed latest on main.
- meta_legacy: ${DH_USER}/py-baleen-<variant>, variant IS the repo name so NO
suffix; standard latest=auto -> `latest` on the default branch.
The build-push step pushes the union of both tag sets. Net result:
dev push -> py-baleen:dev-cpu, py-baleen-cpu:dev (+ sha variants), GHCR
main push -> py-baleen:latest-cpu, py-baleen-cpu:latest (+ main, sha)
latest=auto does not synthesize a `latest` tag for branch/sha generators, so
the legacy py-baleen-cpu/py-baleen-gpu repos would keep their stale f5c-era
:latest on main pushes — defeating the back-compat goal. Declare latest
explicitly (latest=false + type=raw,value=latest,enable={{is_default_branch}}),
matching the new single-repo metadata. Legacy repos carry no -cpu/-gpu suffix
since the variant is the repo name.
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
1 participant
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
Before the single-repo switch, images lived in separate Docker Hub repos
btrspg/py-baleen-cpuandbtrspg/py-baleen-gpu. Those still hold stale f5c-era images that users/scripts may still pull. Keep them in sync by pushing every build to the legacy repos too, alongside the new singlepy-baleenrepo.How
Each build job runs two
metadata-actionsteps and the build-push step pushes the union:meta→${DH_USER}/py-baleen+ghcr.io/<owner>/py-baleen, variant as a tag suffix (-cpu/-gpu), explicit per-tag-suffixedlateston main.meta_legacy→${DH_USER}/py-baleen-<variant>, variant is the repo name so no suffix; explicitlatestgated to the default branch.Resulting tags
py-baleenpy-baleen-cpu/-gpudev-cpu/dev-gpu(+sha):dev(+sha)latest-cpu/latest-gpu(+sha):latest,:main(+sha)Codex flagged (and this fixes) that
latest=autowon't synthesizelatestfor branch/sha generators — both new and legacy now use an explicittype=raw,value=latest,enable={{is_default_branch}}.Note
The legacy repos refresh only after this merges to dev (CI is push-triggered), which will also bring their
:devup to the current code (incl. the readdb fix).Test plan
py-baleen:dev-{cpu,gpu},py-baleen-cpu:dev,py-baleen-gpu:dev, and GHCR