Draft
Conversation
Contributor
|
What could help with this is if the dates were taken into account too (if necessary). 1.5.6a1 And it means the opposite with 1.4.5 For fetch: at least, dates are usually available in the same page as the version listings. |
Owner
Author
|
Good points, hmm for git i think you probably have to digg into commit blobs etc to see dates, not sure i would like to do that. As you said about pre-release/patch-release, version sort would probably also need to kind of both constraint like semver and config how to interpret some columns. Tricky, will have to think about this a bit. |
Closed
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.