-
Notifications
You must be signed in to change notification settings - Fork 653
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] Tag versioning fails if newer 'release' branch exists #2869
Comments
Log attached (it refers to 'production' module, instead of 'web' as stated in OP for clarity):
|
Are you able to reproduce this in a failing test in a PR? |
GitVersion producing version numbers that contain the word |
I tried to build a test case but couldn't reproduce the issue. Sorry for not updating. Will try the parched version once is released and let you know about the result. |
🎉 This issue has been resolved in version 5.10.0 🎉 Your GitReleaseManager bot 📦🚀 |
Fix for this bug was reverted in 5.10.1 release (see: #3085). Can you re-open the bug? I tried latest version of the tool and it is setting version based on the release branch name, instead of the tag. It works as expected in version 5.10.0 |
Describe the bug
When using TBD and following configuration in gitversion file
When a new release branch is created (for example
release/web/0.19
) gitversion works fine when a new tag has been created (for example tagweb/0.19.3
).A few days ago a new branch
release/web/1.0
was created in order to get ready for launchToday a new PR with a fix is pushed to
release/web/0.19
and the build is named correctly:0.19.4-qa.4
Then a new tag is created for this patch version:
web/0.19.4
.Now gitversion fails giving the right name to the build. It names the build as
#1.0.0-tags-production-0-19-4.1+29
Expected Behavior
Build should be named using the new tag
Actual Behavior
Builds are tagged using as base version the newer release branch instead the one where the tag has been created
Possible Fix
Use the version number in tag, if it has been created in the release branch for same major.minor version
Steps to Reproduce
main
0.1
0.1.0
1.0
main
, then cherry pick torelease/0.1
0.1.1
Context
Your Environment
Azure DevOps Server 2020
The text was updated successfully, but these errors were encountered: