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
This is problematic because many versions are date allocated in dev ops use cases.
NewVersion parsed these correctly before and this change will cause large problems for our existing versions. While not in spec, it is a common usage.
Since there is already the concept of StrictNewVersion and NewVersion, it seems like a bad idea to alter NewVersion like this.
Thoughts?
The text was updated successfully, but these errors were encountered:
Just run into a similar issue today after upgrading semver from v3.3.0 to v3.3.1
The version "0.09.00" cannot be parsed any anymore. We have third party Helm charts which unfortunately have such a version string.
Sorry, something went wrong.
No branches or pull requests
This is problematic because many versions are date allocated in dev ops use cases.
NewVersion parsed these correctly before and this change will cause large problems for our existing versions. While not in spec, it is a common usage.
Since there is already the concept of StrictNewVersion and NewVersion, it seems like a bad idea to alter NewVersion like this.
Thoughts?
The text was updated successfully, but these errors were encountered: