-
Notifications
You must be signed in to change notification settings - Fork 46
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.
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
Incrementing #10
Comments
I had no actual plans to include versioning incrementing, but if you contribute the functionality, I certainly welcome it. |
What are people's thoughts on an Also, what should happen to the prerelease and build metadata when incrementing. I'm kind of thinking they should be cleared, but I can imagine situations where you wouldn't want that. |
An alternative API would be a Another question is how these should handle starting from prerelease. For example |
I prefer the fixed methods
I dont think metadata or prereleases should be kept. A new version definitely signals a new build context (new (or the same) metadata can be added in a second call if needed). Prereleases should also be cleared in my opinion, as they refer to the patch version instead of the minor in case of a bump. |
Glad to find this library does most things -- are there plans to align versioning incrementing with semver 2.0.0?:
semver
incrementing major does not zero minor and patch.(I will add it of you're interested.)
The text was updated successfully, but these errors were encountered: