Link the ghcr package to the repo via the OCI source label - #3
Draft
lllamnyp wants to merge 1 commit into
Draft
Conversation
ghcr.io links a container package to its repo through org.opencontainers.image.source, and the link is what grants the repo's Actions workflows write access. The package was first created by a manual push, so it came up user-scoped and the release workflow's GITHUB_TOKEN was denied (write_package). Carrying the label in the image keeps the link re-establishable from any push path, including local make docker-push. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>
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.
ghcr.io links a container package to its repository through the
org.opencontainers.image.sourcelabel, and that link is what grants the repository's Actions workflows write access to the package. The package was first created by a manual push, so it came up user-scoped and the release workflow'sGITHUB_TOKENwas denied (permission_denied: write_package). The link has been established out-of-band by a labeled push; carrying the label in the Dockerfile keeps it re-establishable from any push path, including a localmake docker-pushto a freshly-recreated package.🤖 Generated with Claude Code