-
Prerequisites
GitVersion packageGitVersion.Tool GitVersion versionOperating systemWindows What are you seeing?Hi. I ran into a problem when updating gitversion from 5.8.2 to 6.0.4 on our build server. The problem is that version for "old" branches (v-10, v-11, v-12) suddenly become to evaluate from tag inside default (master) branch. For example, master has the latest tag 20.1.5 and branch v-11 has its latest tag 11.7.0 so making a new commit into v-11 I expect to get version 11.7.1. So it was before upgrading to gitversion 6.0.4. After upgrade I have version 20.1.6. I spent some time on reading release notes/breaking changes with no luck. Then I started to check commit by commit in version history to localize the problem and have come to #3441. Consider taking https://github.com/destructurama/attributed repo as an example:
Now I expect 4.1.1 output from gitversion. My results (with stripped out time marks and execution time to make diff cleaner):
OK, 4.1.1
Not OK, 5.1.0. Since that commit I can observe such behaviour. I think that corresponding part of problem in logs can be seen here: ![]() What is expected?I expect gitversion to use tags from working branch when operating on that branch, not from default branch. Steps to ReproduceConsider taking https://github.com/destructurama/attributed repo as an example:
RepositoryFixture TestNo response Output log or link to your CI build (if appropriate). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
Actually, I would expect the version 5.1.1 as a result. This is the behavior I have tested with gitversion 6.3.0. The test branch is an unknown branch which will be treated almost like a feature branch (there are some difference). All tags on main are recognized when you are developing a new fetaure on e.g. a feature branch. Please see the GitFlow configuration: https://gitversion.net/docs/reference/configuration |
Beta Was this translation helpful? Give feedback.
Is this not exactly the use case of support branches?
https://gitversion.net/docs/learn/branching-strategies/gitflow/examples#support-branches