ci: add scheduled pruning of old untagged GHCR versions#3153
Merged
Conversation
Staging rebuilds accumulate thousands of untagged container versions on ghcr.io (staging-kernelci alone reached ~9000). Add a weekly workflow deleting untagged versions older than 180 days. Tagged manifests are resolved through the registry API first, so per-arch children of multi-arch indexes are never deleted. The job runs with the default GITHUB_TOKEN (packages: write) and supports manual dispatch with a dry-run flag and configurable age cutoff. Signed-off-by: Denys Fedoryshchenko <denys.f@collabora.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.
Staging rebuilds accumulate thousands of untagged container versions on ghcr.io (staging-kernelci alone reached ~9000). Add a weekly workflow deleting untagged versions older than 180 days.
Tagged manifests are resolved through the registry API first, so per-arch children of multi-arch indexes are never deleted. The job runs with the default GITHUB_TOKEN (packages: write) and supports manual dispatch with a dry-run flag and configurable age cutoff.