Stop auto-deleting container package versions#585
Merged
Conversation
mjudeikis
force-pushed
the
stop-deleting-packages
branch
2 times, most recently
from
051da49 to
63ede75
Compare
Signed-off-by: Mangirdas Judeikis <mangirdas@judeikis.lt>
mjudeikis
force-pushed
the
stop-deleting-packages
branch
from
63ede75 to
7ee34c1
Compare
cnvergence
approved these changes
Jul 7, 2026
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.
What
Removes the three
actions/delete-package-versionssteps from.github/workflows/image.yamlthat pruned old pre-release versions ofkonnector,backend, andcharts/backend.Why
This workflow runs on every push to
main(andv*tags). The cleanup steps were firing on each merge and deleting container image versions we want to keep — surfacing as recurringgithub-actions[bot]→packages.package_version_deletedaudit events.Removing the auto-prune; retention can be managed manually (or re-added later scoped to tags only, with a higher
min-versions-to-keep) if disk usage ever becomes a concern.