Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"1.0" should be considered a valid semver number #855

Closed
andrew opened this issue Nov 2, 2016 · 1 comment
Closed

"1.0" should be considered a valid semver number #855

andrew opened this issue Nov 2, 2016 · 1 comment
Labels
bug roadmap small

Comments

@andrew
Copy link
Contributor

andrew commented Nov 2, 2016

If the number can be expanded into a proper MAJOR.MINOR.PATCH number then it should be considered valid, current affects the source rank of quite a few ruby libraries.
@andrew andrew added the bug label Nov 2, 2016
@andrew andrew assigned andrew and unassigned andrew Nov 14, 2016
@andrew andrew added the small label Feb 21, 2017
@andrew andrew added the roadmap label Oct 9, 2017
@andrew
Copy link
Contributor Author

andrew commented Oct 9, 2017

Moving this to the Backlog as we'd still like to implement it but can't see that happening in the near future.

@andrew andrew closed this as completed Oct 9, 2017
@techtonik techtonik mentioned this issue Aug 29, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug roadmap small
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andrew