-
Notifications
You must be signed in to change notification settings - Fork 34
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
npm run release -- --release-as 1.0.0 as first release ends up with 1.1.0 #51
Comments
Hmm. This is unexpected. What is the What happens if you remove that tag and commit and do:
(note no double Are there any tags in this repository already? |
I tested Is there a reason for the extra |
You need those with |
You're right, nr isn't just I copied the Thanks for the help! |
You're welcome! Glad it got fixed! |
Describe the bug
npm run release -- --release-as 1.0.0 as first release ends up with 1.1.0. Maybe I'm missing something but I thought I would get 1.0.0 and not 1.1.0.
Current behavior
After running npm run release -- --release-as 1.0.0 as the first ever release, the tag ends up as 1.1.0.
Expected behavior
After running npm run release -- --release-as 1.0.0 as the first ever release, the tag ends up as 1.0.0.
Environment
Possible Solution
Additional context
![Code_15_22-49-22JNpFnmtd3j](https://user-images.githubusercontent.com/110549389/212569077-e64b6313-7a96-4e4c-a7a0-da20a945e1a9.png)
Add any other context about the problem here. Or a screenshot if applicable
Maybe this is not how you're supposed to use commit-and-tag-version so I'm open for any solutions. 😄
The text was updated successfully, but these errors were encountered: