Repository navigation
ci: use GITHUB_TOKEN to clean up registry - #89
Merged
Merged
Conversation
The IMAGES_CLEANUP_TOKEN secret can list package versions but cannot delete them, so the workflow failed whenever a branch image existed. The workflow token with packages write permission can delete them. Assisted-by: Claude Code:Opus 5.5
38 of 44 tasks
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.
The "Clean up registry" workflow should delete a branch's container images when the branch is deleted, but it always fails because the
IMAGES_CLEANUP_TOKENsecret is not allowed to delete them. See NethServer/dev#8222.The workflow now uses the token GitHub provides to each workflow run, with explicit permission to write packages.
How to test
DELETEnotice per imageGenerated by Claude Code:claude-opus-5-5 with nethserver-pr