it doesn't seem to bump the version correctly

[vishu42]

take a look at the git log

vishaltewatia@Vishal-SS378 react-native-calendars % git log
commit 6b234273deddfbb95540f3de85cf98b034c41b74 (HEAD -> develop, tag: 1.2.0)
Author: vishu42 <[email protected]>
Date:   Fri Jan 7 14:38:51 2022 +0530

    +semver: fix

commit fc02d87afcc8080d73a73c7d3be0369c7264a424 (tag: 1.1.0)
Author: vishu42 <[email protected]>
Date:   Fri Jan 7 14:38:16 2022 +0530

    +semver: patch

commit 3bf97e1a98d724fd9dce1a956f8e0b1585b89de8 (tag: 1.0.0)
Author: vishu42 <[email protected]>
Date:   Fri Jan 7 14:37:50 2022 +0530

    init

I manually generated the initial tag 1.0.0, then i made a commit +semver: patch and ran gitversion /showvariable SemVer | xargs git tag , the incremented tag is supposed to be 1.0.1 but its incrementing minor version.

Below is the GitVersion.yml file

assembly-versioning-scheme: MajorMinorPatch
assembly-file-versioning-scheme: MajorMinorPatch
mode: ContinuousDelivery
tag-prefix: '[vV]'
continuous-delivery-fallback-tag: ci
major-version-bump-message: '\+semver:\s?(breaking|major)'
minor-version-bump-message: '\+semver:\s?(feature|minor)'
patch-version-bump-message: '\+semver:\s?(fix|patch)'
no-bump-message: '\+semver:\s?(none|skip)'
legacy-semver-padding: 4
build-metadata-padding: 4
commits-since-version-source-padding: 4
tag-pre-release-weight: 60000
commit-message-incrementing: Enabled
branches:
  develop:
    mode: ContinuousDelivery
    tag: ''
    increment: Minor
    prevent-increment-of-merged-branch-version: false
    track-merge-target: true
    regex: ^dev(elop)?(ment)?$
    source-branches: []
    tracks-release-branches: true
    is-release-branch: true
    is-mainline: false
    pre-release-weight: 0
  main:
    mode: ContinuousDelivery
    tag: ''
    increment: Patch
    prevent-increment-of-merged-branch-version: true
    track-merge-target: false
    regex: ^master$|^main$
    source-branches:
    - develop
    - release
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: true
    pre-release-weight: 55000
  release:
    mode: ContinuousDelivery
    tag: beta
    increment: None
    prevent-increment-of-merged-branch-version: true
    track-merge-target: false
    regex: ^releases?[/-]
    source-branches:
    - develop
    - main
    - support
    - release
    tracks-release-branches: false
    is-release-branch: true
    is-mainline: false
    pre-release-weight: 30000
  feature:
    mode: ContinuousDelivery
    tag: useBranchName
    increment: Inherit
    prevent-increment-of-merged-branch-version: false
    track-merge-target: false
    regex: ^features?[/-]
    source-branches:
    - develop
    - main
    - release
    - feature
    - support
    - hotfix
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: false
    pre-release-weight: 30000
  pull-request:
    mode: ContinuousDelivery
    tag: PullRequest
    increment: Inherit
    prevent-increment-of-merged-branch-version: false
    tag-number-pattern: '[/-](?<number>\d+)'
    track-merge-target: false
    regex: ^(pull|pull\-requests|pr)[/-]
    source-branches:
    - develop
    - main
    - release
    - feature
    - support
    - hotfix
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: false
    pre-release-weight: 30000
  hotfix:
    mode: ContinuousDelivery
    tag: beta
    increment: Patch
    prevent-increment-of-merged-branch-version: false
    track-merge-target: false
    regex: ^hotfix(es)?[/-]
    source-branches:
    - develop
    - main
    - support
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: false
    pre-release-weight: 30000
  support:
    mode: ContinuousDelivery
    tag: ''
    increment: Patch
    prevent-increment-of-merged-branch-version: true
    track-merge-target: false
    regex: ^support[/-]
    source-branches:
    - main
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: true
    pre-release-weight: 55000
ignore:
  sha: []
commit-date-format: yyyy-MM-dd
merge-message-formats: {}
update-build-number: true

[HHobeck]

The bump message increment behaves different depending on whether you run it on branches with mainline or non-mainline mode. In this case I expect you are in a branch with ContinuousDelivery mode with increment Minor and complaining about that the commit message semver+: patch not considered right!?

The bump message feature like it is implemented in the actual version of git-version is there to bump the increment to a higher value for the calculation of the next version. If lets say the base version is 1.0.0 then the following matrix applies:

A commit without a bump message yields:

• on branches with increment none to 1.0.0
• on branches with increment patch to 1.0.1
• on branches with increment minor to 1.1.0
• on branches with increment major to 2.0.0

A commit with semver+: patch message yields

• on branches with increment none to 1.0.1
• on branches increment patch to 1.0.1
• on branches increment minor to 1.1.0
• on branches increment major to 2.0.0

A commit with semver+: minor message yields

• on branches with increment none to 1.1.0
• on branches with increment patch to 1.1.0
• on branches with increment minor to 1.1.0
• on branches with increment major to 2.0.0

A commit with semver+: major message yields

• on branches with increment none to 2.0.0
• on branches with increment patch to 2.0.0
• on branches with increment minor to 2.0.0
• on branches with increment major to 2.0.0

You need to think about the use case of using the bump message feature. The motivation is more dependent on what changes your commit includes from the development perspective. When you in the role of a developer don't care about what the target branch might be and think: "Oh it's not just a minor change it’s a huge change which should yield to a major version increment because I have updated the API with a breaking change." Hope that's understandable.