-
Notifications
You must be signed in to change notification settings - Fork 652
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
[Bug] SemVer of a feature branch started from a release branch gets decremented #3151
Comments
|
So the idea is that stabilizing a |
Yes, or by merging more |
Could this be considered a future improvement? It is not explicitly stated how bugfixes should be done on |
It not rare to have rules on projects that only allow changes through pull requests. Especially on release branches as they tend to generate releasable artifacts. Also, as @ni-jsuchocki said, if a team is big enough, it is also common to have new development on develop while stabilization work is happening on the release branch. So we might not want the new changes from develop while stabilizing the release branch. |
Sure, I understand that. But I don't see a way to tell GitVersion to have An alternative would be to name the release-stabilizing branches differently from |
Please see the discussion in #3101. |
Please take a look and tell me if you are agree with this test (see integration test here). Two commits have been pushed after you entered the beta phase that's why +2 IMO |
Hi @HHobeck, sorry for not reaching out earlier but thanks a lot for the changes you've done here! I finally found some time to play around with the current state of the code and your changes seem to really improve on a couple of issues we were encountering earlier! Can't wait for the 6.0 release :) |
🎉 This issue has been resolved in version 6.0.0 🎉 Your GitReleaseManager bot 📦🚀 |
Describe the bug
Hello! We are using GitVersion with the GitFlow branching scheme. I'd expect that the feature branch started from a release branch has the same SemVer as the parent release branch.
Expected Behavior
SemVer of a commit on a feature branch is the same as the SemVer of a parent release branch.
Actual Behavior
SemVer gets decremented to the previous release version.
Steps to Reproduce
Context
I know this can be fixed by setting
tracks-release-branches: true
for therelease
branch type, but this has other consequences as well - for example if arelease/2.0.0
branch is started in the same repo, the SemVer of a build from a feature branch will be2.0.0
even if its parent branch isrelease/1.1.0
.Also looking at the docs for
track-release-branches
-Indicates this branch config represents develop in GitFlow.
- I am wary to change it for release branches.It looks as it should be the default behaviour for me, but am I missing some other configuration options that would change this?
Your Environment
main
at5.10.4-beta.1+41.Branch.main.Sha.68604754376c7df1d7a378a3a29fb92d55dd3013
, same behavior is observed in our CI where5.8.2
is installedThe text was updated successfully, but these errors were encountered: