Repository navigation
ci: sort release tags by version, not lexicographically - #1200
Merged
Merged
Conversation
corkamig
approved these changes
Oct 16, 2026
williballenthin
approved these changes
Oct 16, 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
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 v10.0.0 release workflow failed (https://github.com/mandiant/capa-rules/actions/runs/38912748434) with "body is too long (maximum is 125000 characters)".
create_releases.pylisted tags withgit tag -l v*.*, which sorts lexicographically, sov10.0.0landed betweenv1.6.1andv2.0.0and the release notes diffed againstv1.6.1. The-poption was also broken for v10+ because the computed range was negative.Use
--sort=v:refname. Verified locally:create_releases.py v10.0.0and-p v9.4.0 v10.0.0both now diff againstv9.4.0, matching the manually created v10.0.0 release notes.