We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
0.16.0
1.0.0
Hi, I love this project, but I have a question.
Why do use a minor patch number to ship an update with breaking changes and a complete rewrite?
For this exact case SemVer says, that the major version number should be shifted.
I saw the update and read the changelog and then wondered why this kind of change isn't called 1.0.0 instead of 0.16.0?
Anyway, now it can't be undone. But I leave this here just to check if you had a reasoning to call it 0.16.0.
It is your project so you can do what you want, and it doesn't change anything about the software itself, but i was just wondering.
The text was updated successfully, but these errors were encountered:
Never mind, didn't see #1857, my bad
Sorry, something went wrong.
No branches or pull requests
How can we improve the documentation?
Hi, I love this project, but I have a question.
Why do use a minor patch number to ship an update with breaking changes and a complete rewrite?
For this exact case SemVer says, that the major version number should be shifted.
I saw the update and read the changelog and then wondered why this kind of change isn't called
1.0.0
instead of0.16.0
?Anyway, now it can't be undone. But I leave this here just to check if you had a reasoning to call it
0.16.0
.It is your project so you can do what you want, and it doesn't change anything about the software itself, but i was just wondering.
The text was updated successfully, but these errors were encountered: