ci(release): move docker buildx registry cache off the zilla image package - #2440
Merged
Merged
Conversation
…ckage cache-to with type=registry publishes the buildx layer cache as a real manifest under the given ref, so it was showing up as extra buildcache/ buildcache-alpine versions in the public ghcr.io/aklivity/zilla package. Point cache-from/cache-to at a dedicated ghcr.io/aklivity/zilla-buildcache package instead, keeping the release image's package limited to real release versions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TPozwovLazfMf5d1ei5MmL
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.
Description
The release workflow's
docker/build-push-actionsteps usecache-to: type=registry,...,mode=maxfor the multi-arch buildx layer cache. That backend publishes the cache as a real manifest under the given ref, which was landing as extrabuildcache/buildcache-alpineversions inside the publicghcr.io/aklivity/zillapackage alongside the actual release images.This moves
cache-from/cache-tofor both the main and alpine image builds to a dedicatedghcr.io/aklivity/zilla-buildcachepackage (:latestand:alpinetags), keepingghcr.io/aklivity/zillalimited to real release versions.type=registryis kept rather than switching totype=gha, since GitHub Actions cache's per-repo size cap and multi-platform scope collisions were the reason this repo moved to the registry backend in the first place.Note: the first release run after this merges will create a new
zilla-buildcachepackage in GHCR. Its visibility will need to be manually confirmed/set to private in the org's package settings, since new packages don't automatically inherit the source repo's visibility.Generated by Claude Code