Releases on same day with equal SemVer priority are out of order #16536
Unanswered
UsernameFodder
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
On my repository's releases page, release v0.2.1+f6de550f13 is marked as the latest release, even though v0.2.1+f6058565b3 was made after it chronologically (on the same day):
Note that the tags are properly ordered, with v0.2.1+f6058565b3 being the latest:
My understanding from discussions like #8226 are that releases made on the same day should be ordered according to SemVer, and I would expect ties to be broken by tag (commit) time. In this case, both versions are v0.2.1, and the build metadata should not contribute to priority according to the spec, but it seems like the releases here are being sorted alphabetically rather than chronologically.
Beta Was this translation helpful? Give feedback.
All reactions