[Bug] Build number in Azure DevOps wrong

[KiLLeRRaT]

Describe the bug
The build number in Azure DevOps has changed and most likely not respecting my GitVersion.yml file anymore.

Expected Behavior

The build number should be 2.4.0-beta.24 when building off a tag called 2.4.0-beta.24.

Actual Behavior

The build number is set to 2.4.0-tags-2-4-0-beta-24.1 when building off of the tag 2.4.0-beta.24

Possible Fix

This seems to have been introduced in 5.12.0. If I revert back to 5.11.x, it works as it should. Could this somehow be related to the prerelease tag changes that were made? Is it because I don't have a beta tag against the master branch in my config but I'm specifying it in a tag or something?

Here is the compare between the two versions for reference: 5.11.1...5.12.0

Context

this is making a mess of my NuGet packages, as they are all now submitted with the weird version.

Your Environment

• Version Used: 5.12.0
• Operating System and version (Windows 10, Ubuntu 18.04): Azure DevOps, agent vmImage: 'windows-latest', .NET 6.0

My GitVersion.yml file:

assembly-versioning-scheme: Major
assembly-informational-format: '{Major}.{Minor}.{Patch}{PreReleaseTagWithDash}+{CommitsSinceVersionSource}.Branch.{EscapedBranchName}.Sha.{ShortSha}'
mode: ContinuousDelivery
increment: Inherit
#tag-prefix: '[vV]'
branches:
    master:
        regex: ^master
        mode: ContinuousDelivery
        tag: ''
        increment: Patch
        prevent-increment-of-merged-branch-version: true
        track-merge-target: false
        tracks-release-branches: false
        is-release-branch: true
    release:
        regex: ^releases?[/-]
        mode: ContinuousDelivery
        tag: beta
        increment: Patch
        prevent-increment-of-merged-branch-version: true
        track-merge-target: false
        tracks-release-branches: false
        is-release-branch: true
    feature:
        regex: ^features?[/-]
        mode: ContinuousDeployment
        tag: alpha
        increment: Minor
        prevent-increment-of-merged-branch-version: false
        track-merge-target: false
        tracks-release-branches: false
        is-release-branch: false

[asbjornu]

Seems like this is related to #2074, #2301, #2838, #2852, #3104 and probably more, which should have been fixed in #3033. In particular, #3033 (comment) may be of interest. I don't think @ThomasPiskol managed to automate testing of that, so perhaps we've somehow reverted his fixes somehow?

[ausarb]

@asbjornu - I can confirm that we had this problem with 5.12.0 (5.x as of this comment) where our master is tagged as 3.0.0 but NuGetVersionV2 is 3.0.1-tags-3-0-0-0001. When I updated our GitHub Actions step to specifically use 5.10.0, the tag build produced a NuGetVersionV2 of 3.0.0 as desired.

[KiLLeRRaT]

Any ideas on how to get around this one guys? Or is it going to have to be another fix?

Thanks!

[JDCain]

I am seeing this issue as well. Anything built off of a tag adds the -tags---*- into the prerelease tag

[HHobeck]

May I ask you to create an integration test (like in Figure 1) to reproduce your issue?

Figure 1: Example of an Integration Test

[KiLLeRRaT]

I will give this a shot, but I may not get around to it in a few weeks :( sorry!

[HHobeck]

I'm going to close this issue because of missing steps to reproduce. Please try your scenario on the preview version 6.0.0-beta.1 which reflects the latest develop initiaitves and give me feedback if your issue still persists. Thank you very much.

[fbernack]

I'm facing the same issue using version 5.12.x and also using 6.0.0-beta.1. Reverting to 5.11.x solved it for me.