Repository navigation
CI: stratified artifact retention, delete transport artifacts - #48
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 three release artifacts (bundle, JDBC repo, combined libsqlite3) now carry stratified retention: 60 days for tag runs, 14 for main, 3 otherwise.
The five per-platform library artifacts are transport only: their bytes ship inside those three artifacts. Their uploads now expire in 1 day as a backstop, and a final step in the artifacts job deletes them from the run once packaging is done (continue-on-error, so a failed delete never fails the build; the job gains actions: write permission for it).