-
Notifications
You must be signed in to change notification settings - Fork 792
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
Using both prelease and release-as parameters, the version number becomes null #542
Open
wwh0219 opened this issue
Feb 10, 2020
· 0 comments
· Fixed by absolute-version/commit-and-tag-version#8 · May be fixed by #767
Open
Using both prelease and release-as parameters, the version number becomes null #542
wwh0219 opened this issue
Feb 10, 2020
· 0 comments
· Fixed by absolute-version/commit-and-tag-version#8 · May be fixed by #767
Comments
kf6kjg
added a commit
to kf6kjg/standard-version
that referenced
this issue
Jun 1, 2021
Previously, as shown in conventional-changelog#542, using both options at the same time resulted in the bump file's version being set to null. This was validated in the first of the new unit tests. The other unit tests simply check that the rest of the behavior is correct in this case. With this combination the user can override the version, the purpose of `release-as`, while still starting or continuing a pre-release, the purpose of of the `prerelease`. Fixes conventional-changelog#542
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There was a problem when I specified a new pre-release version number
The text was updated successfully, but these errors were encountered: