completely delete SNAPSHOT packages before deploying new SNAPSHOT version #972
Conversation
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
chrjohn
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Github Packages accumulates packages since each SNAPSHOT version has a new timestamp.
See actions/delete-package-versions#71 or https://stackoverflow.com/questions/68521637/how-to-delete-old-snapshot-artifacts-from-github-packages
SNAPSHOT versions have a distinct timestamp in the repo, but the github action sees all these packages as belonging to the same version, so specifiying a minimum number of versions to keep does not work. So we simply tell the action to keep
0versions.To minimize the time in which there is no version available on github packages we will do: