release notes need to be in semver order, not alpha#277
Merged
Conversation
heskew
force-pushed
the
release-notes-sidebar-order
branch
from
5b30259 to
727e6f7
Compare
There was a problem hiding this comment.
Pull Request Overview
This PR fixes the release notes ordering by implementing semantic version-based sorting instead of alphabetical ordering. The change ensures that release notes are displayed in descending semantic version order (newest first) rather than simple alphabetical order.
Key changes:
- Replaced simple
.reverse()with custom semantic version sorting logic - Added version string parsing and padding for proper numerical comparison
- Maintained filtering of index files while improving sort order
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Member
Author
|
merging now to get this display bugfix in |
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.
No description provided.