-
Notifications
You must be signed in to change notification settings - Fork 650
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] Merging develop to release branch makes alpha version jump back #3154
Labels
Milestone
Comments
franknarf8
changed the title
[Bug]
Merging develop to release branch makes alpha version jump back
Jul 19, 2022
franknarf8
changed the title
Merging develop to release branch makes alpha version jump back
[Bug] Merging develop to release branch makes alpha version jump back
Jul 20, 2022
I think you may be affected by #3041. |
I have tested your integration test on the PR #3190 and it's working like you would expecting it IMO. |
5 tasks
🎉 This issue has been resolved in version 6.0.0 🎉 Your GitReleaseManager bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hello again dear GitVersion maintainers :)
When getting the changes from the
develop
branch on top of an existingrelease
branch, the commit counting ofdevelop
drops as the Merge Base commit changes.Expected Behavior
The commit counting on
develop
should never drop, otherwise this generates overlapping build numbers.Actual Behavior
Workaround
Context
Creating a beta tag (e.g.
3.0.0-beta.1
) is then only useful if thedevelop
and therelease
branches are completely independent.I'm not sure how we could implement a fix for this. Finding the base commit from which the metadata value is currently calculated using the vanilla MergeBase functionality of git, which finds the shortest intersection of 2 branches.
Any ideas?
The text was updated successfully, but these errors were encountered: