Picking tags over branch name - why would that be?

[christophwille]

GitVersion package

GitVersion.Tool

GitVersion version

6.1.0

Operating system

Windows

What are you seeing?

We have one gitversion.yml with exactly one line only

workflow: GitFlow/v1

Our release branches are created like release/0.29

Up until 0.28 everything was fine, and then it did this:

INFO [25-01-17 10:05:31:11] Using latest commit on specified branch
INFO [25-01-17 10:05:31:26] Getting tagged semantic versions. TagPrefix: [vV]? and Format: Strict
INFO [25-01-17 10:05:33:29] Running against branch: release/0.29 ('95e946f' - Merged PR 4327: fix spec, event handlers)
INFO [25-01-17 10:05:33:30] -< Begin: Fetching the base versions for version calculation... >-
  INFO [25-01-17 10:05:33:30] -< Begin: Calculating base versions for 'release/0.29' >-
    INFO [25-01-17 10:05:33:30] -< Begin: [Using 'ConfiguredNextVersionVersionStrategy' strategy] >-
    INFO [25-01-17 10:05:33:31] -< End: [Using 'ConfiguredNextVersionVersionStrategy' strategy] (Took: 0.82ms) >-
    INFO [25-01-17 10:05:33:31] -< Begin: [Using 'MainlineVersionStrategy' strategy] >-
    INFO [25-01-17 10:05:33:31] -< End: [Using 'MainlineVersionStrategy' strategy] (Took: 0.64ms) >-
    INFO [25-01-17 10:05:33:31] -< Begin: [Using 'MergeMessageVersionStrategy' strategy] >-
    INFO [25-01-17 10:05:33:36] -< End: [Using 'MergeMessageVersionStrategy' strategy] (Took: 50.97ms) >-
    INFO [25-01-17 10:05:33:36] -< Begin: [Using 'TaggedCommitVersionStrategy' strategy] >-
      INFO [25-01-17 10:05:33:36] -< Begin: Getting tagged semantic versions on branch 'refs/heads/release/0.29'. TagPrefix: [vV]? and Format: Strict >-
      INFO [25-01-17 10:05:33:37] -< End: Getting tagged semantic versions on branch 'refs/heads/release/0.29'. TagPrefix: [vV]? and Format: Strict (Took: 3.09ms) >-
      INFO [25-01-17 10:05:33:41] Git tag '0.23.0': Version increment '0.23.0' +semver 'Minor' with label 'beta' based on commit 'a715274'.
    INFO [25-01-17 10:05:33:41] -< End: [Using 'TaggedCommitVersionStrategy' strategy] (Took: 53.62ms) >-
    INFO [25-01-17 10:05:33:41] -< Begin: [Using 'TrackReleaseBranchesVersionStrategy' strategy] >-
    INFO [25-01-17 10:05:33:41] -< End: [Using 'TrackReleaseBranchesVersionStrategy' strategy] (Took: 0.58ms) >-
    INFO [25-01-17 10:05:33:41] -< Begin: [Using 'VersionInBranchNameVersionStrategy' strategy] >-
    INFO [25-01-17 10:05:33:42] -< End: [Using 'VersionInBranchNameVersionStrategy' strategy] (Took: 4.93ms) >-
  INFO [25-01-17 10:05:33:42] -< End: Calculating base versions for 'release/0.29' (Took: 113.99ms) >-
INFO [25-01-17 10:05:33:42] -< End: Fetching the base versions for version calculation... (Took: 117.52ms) >-
INFO [25-01-17 10:05:33:42] -------------------------------------------------------
INFO [25-01-17 10:05:33:42] Base version used: Git tag '0.23.0': Take '0.23.0' based on commit 'a715274'.

Why is it picking the tag? (the tag is old, was on previous branches as well, but so far GitVersion didn't care)

What is expected?

Could you please give me a hint why that might be happening?

[christophwille]

That is actually not a behavior change... just uninstalled/installed 6.0.4, it behaves exactly the same. Adapted the issue accordingly. Feel free to move it to Discussions.

[HHobeck]

0.29 is not a valid semantic version. Thus in strict mode it will be not considered. You need to either change the semantic-version-format to Loose or name your branch release/0.29.0.

Cheers.

[christophwille]

Thanks! All other branches were named properly, this wasn't - and we didn't realize it.