Repository navigation
release: let the deb artifacts expire after a day - #16
Merged
Merged
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
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.
The org hit 90% of its included Actions storage, and this repo was the single biggest holder — 764 MB of
deb-amd64/deb-arm64artifacts going back to v0.1.0.All of it was dead weight: the artifact only carries the .deb from the build job to the release job, and the same file ends up on the GitHub release right after. Release assets are not metered, so keeping a 90-day copy in Actions storage bought nothing.
retention-days: 1gives the hand-off plenty of room and lets the copy expire.