Repository navigation
fix(ci): sort releases by publication date - #23
Merged
Merged
Conversation
GitHub sets the createdAt of a release to the date of the tagged commit. Every release since 2026.10.24 points to the same commit, so sorting on createdAt gives a tie and the comparison step picked 2026.10.24 instead of the latest release. The size check then compared today's databases with a ten day old one. The prune step had the same sort and could delete the wrong releases. Both now sort on publishedAt. Refs #22
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.
GitHub sets the createdAt of a release to the date of the tagged commit.
Every release since 2026.10.24 points to the same commit, so sorting on
createdAt gives a tie and the comparison step picked 2026.10.24 instead
of the latest release. The size check then compared today's databases
with a ten day old one.
The prune step had the same sort and could delete the wrong releases.
Both now sort on publishedAt.
Refs #22