-
Notifications
You must be signed in to change notification settings - Fork 648
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
[ISSUE]: Semver on release branch containing prerelease number. #4175
Comments
Please see the following example: https://gitversion.net/docs/learn/branching-strategies/gitflow/examples You will find this annotation:
and
|
@HHobeck I don't know whether this will make sense, but I don't want ContinuousDeployment (I want to increment the version for every commit, i.e. ContinuousDelivery) but I would like to prevent the main branch from adding the pre-release tag. Is there a way to do that? If I have a previous commit tagged as 3.7.58 and I put it on ContinuousDeployment, each commit until I change the version will result in the same version as 3.7.58. Is there a way to achieve that? Thank you @Tilusch for asking this, I'm having the same issue. |
Prerequisites
GitVersion package
GitVersion.Tool
GitVersion version
6.0.2
Operating system
macOS
What are you seeing?
After Upgrading my config from Gitversion 5.12.0 to 6.0.2 things broke. I use the following config after going trough the breaking changes:
I use a CI Pipeline to create releases when i push something to the main branch, before i got the following versions on the main branch:
now i get this versions on the main branch
The text was updated successfully, but these errors were encountered: