Versioning is different on main and release branch for the same commit

[kabilanmani93]

command executed on gitversion docker image v6

      # in case the checkout branch name is changed, make sure to update the regex below as well for FULL_SEM_VER_REPLACE 
      echo $CI_COMMIT_REF_NAME
      if [[ "$SEMVER_BRANCH_OVERRIDE" != 'true' ]]; then
        CHECKOUT_BRANCH=master
        if [[ $CI_COMMIT_REF_NAME  =~ ^release* ]]; then
          CHECKOUT_BRANCH=release
        fi
        if [[ $CI_COMMIT_REF_NAME  =~ ^beta* ]]; then
          CHECKOUT_BRANCH=beta
        fi
        git fetch origin $CI_COMMIT_SHA:$CHECKOUT_BRANCH
      else
        echo "Overriding checkout branch by using $CI_COMMIT_REF_NAME"
        CHECKOUT_BRANCH=$CI_COMMIT_REF_NAME
      fi
      # For Projects using LFS , Removing the post-checkout hook as the base gitverion image version doesnt have lfs configured
      rm -rf .git/hooks/post-checkout
      git checkout $CHECKOUT_BRANCH

      /tools/dotnet-gitversion /output buildserver /c $CI_COMMIT_SHA /nonormalize $VERBOSITYSETTING 

Below is my GitVersion.yml

assembly-file-versioning-scheme: MajorMinorPatch
assembly-informational-format: '{InformationalVersion}'
mode: Mainline
branches:
  master:
    regex: ^master$|^main$
    label: ''
    increment: Inherit
    prevent-increment-of-merged-branch-version: true
    source-branches: ['feature', 'release']
    is-source-branch-for: [ 'feature', 'release', 'patch' ]
    is-release-branch: false
    is-mainline: true
  patch:
    regex: '^(patch|bugfix|hotfix)[/-]'
    label: ''
    increment: Patch
    source-branches: ['master', 'main']
    is-source-branch-for: []
  release:
    regex: ^release?[/-]
    label: 'hotfix'
    prevent-increment-of-merged-branch-version: true
    source-branches: [ 'main', 'master' ]
    tracks-release-branches: false
    is-release-branch: true
    is-mainline: false
    is-source-branch-for: []
  beta:
    regex: ^beta[/-]
    label: 'Beta'
    prevent-increment-of-merged-branch-version: true
    increment: None
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: false
    source-branches: [ 'master', 'main' ]
    is-source-branch-for:  [ 'feature', 'patch' ]
  maintenance:
    regex: ^maintenance[/-]
    increment: Patch
    is-mainline: true
    prevent-increment-of-merged-branch-version: true
    source-branches: ["main"]
  feature:
    regex: ^feature[/-]
    label: ''
    increment: Minor
    prevent-increment-of-merged-branch-version: false
    track-merge-target: false
    source-branches: ['master', 'main']
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: false
    is-source-branch-for: []

On the same commit id , which i checkout to main and release branches. the gitversion generated is different

On main it is 0.290.0
on release it is 0.290.0-hotfix.52

when i checked the logs for release branch, the source commit is different

    INFO [09/05/24 15:29:00:25] Begin: Finding branch source of 'origin/release/0.290.0'
      INFO [09/05/24 15:29:00:26] Begin: Finding merge base between 'origin/release/0.290.0' and 'origin/main'.
        INFO [09/05/24 15:29:00:26] Found merge base of 1e283ad Merge branch 'feature/MOB-2143-sums-datahub' into 'main'
        INFO [09/05/24 15:29:00:26] Merge base was due to a forward merge, next merge base is 9d23fa9 Merge branch 'feature/MOB-000-cleanup-add-tags-in-stg-prd' into 'main'
        INFO [09/05/24 15:29:00:26] Merge base was due to a forward merge, next merge base is 0a3df85 Merge branch 'feature/MOB-1641-DD-yml-changes' into 'main'
        INFO [09/05/24 15:29:00:27] Merge base was due to a forward merge, next merge base is 70356a4 bugfix-back-old-env-changes
        INFO [09/05/24 15:29:00:27] Merge base of origin/release/0.290.0' and 'origin/main is 70356a4 bugfix-back-old-env-changes
      INFO [09/05/24 15:29:00:27] End: Finding merge base between 'origin/release/0.290.0' and 'origin/main'. (Took: 7.14ms)
    INFO [09/05/24 15:29:00:27] End: Finding branch source of 'origin/release/0.290.0' (Took: 16.61ms)
    INFO [09/05/24 15:29:00:27] Version in branch name: 0.290.0 with commit count source 70356a4170a14d39873bdf3597cbddfdce4f49a0
    INFO [09/05/24 15:29:00:27] Using current branch name to calculate version tag
    INFO [09/05/24 15:29:00:27] Found multiple base versions which will produce the same SemVer (0.290.0-release.1), taking oldest source for commit counting (Version in branch name)
    INFO [09/05/24 15:29:00:27] Base version used: Version in branch name: 0.290.0 with commit count source 70356a4170a14d39873bdf3597cbddfdce4f49a0
  INFO [09/05/24 15:29:00:27] End: Calculating the base versions (Took: 1,066.14ms)
  INFO [09/05/24 15:29:00:27] Begin: Using manual deployment workflow to calc
ulate the incremented version.

[asbjornu]

This is all just as designed and as you've configured. What output do you expect? The reason the commit is different on main and the release branch might be due to the following:

INFO [09/05/24 15:29:00:27] Found multiple base versions which will produce the same SemVer (0.290.0-release.1), taking oldest source for commit counting (Version in branch name)

[HHobeck]

The mode: Mainline and others things in your configuration are not a valid for gitversion 6. Please us the workflow property and try to reproduce your issue with the default workflow template:

workflow: GitFlow/v1

(see docs/input/docs/workflows/TrunkBased/preview1.yml)

I'm closing this issue. Please feel free to create a new discussion.