-
Notifications
You must be signed in to change notification settings - Fork 30
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
version
is not working properly on prerelease
#149
Comments
I have to test this out. I think there is a bug that when there is a tag v0.2.2 the bump pre-release should always be 0.2.3-rc.1 or 0.3.0-rc1. I am not sure what should be the behavior if there are no fix/feat or breaking changes. |
Is there a way to add/introduce custom config so that parse other commits used as patch/minor/major? |
Not implemented as not in the spec. |
Sorry to answer late, but i don't have much free time. #!/bin/env sh
set -x
rm -rf .git
convco version
git init .
convco version
git commit --allow-empty -m 'hotfix: correct ..'
convco version
git tag v0.2.2
convco version
git commit --allow-empty -m 'chore: release'
git commit --allow-empty -m 'perf: use precompiled binary'
convco version --bump --prerelease rc The last output is indeed |
I think that in this case the issue is that there is no commit that increments the version by convention. |
For point 7 I cannot reproduce.
The last command prints |
Describe the bug
I think
version
is notbump
prerelease versions correctly & does not display the correctcurrent
version as well.To Reproduce
v0.2.2
.convco
to get nextprerelease
:prelease
tag. Also, I runversion
fix: test
step 3
# version `v0.2.3-rc.1`
step-3 & step-4
with a new commitfix: test1
Also run the.
version
again.Expected behavior
I was excepting to bump a version as
v0.2.2-rc.2
,v0.2.2-rc.3
not as a new version & not bumping at all.Also current version should change as well.
System (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: