Why is the patch version not auto incrementing when using GitVersion?

Question

I'm using Azure pipelines to set a version number using GitVersion. Here is the pipeline:

    - task: gitversion/setup@0
      displayName: 'Setup GitVersion'
      inputs:
        versionSpec: '5.x'
    
    - task: gitversion/execute@0
      displayName: 'Run GitVersion'
      inputs:
        useConfigFile: true
        configFilePath: 'GitVersion.yml'

It seems to run without any problems but the patch number is never incremented. It doesn't work when I add +semver: patch to the commit message either.

It seems the FullSemVer is affected: 0.8.0+11
But I'm expecting: 0.8.11

Here is the GitVersion.yml file

next-version: 0.7.0
assembly-versioning-scheme: MajorMinorPatch
assembly-file-versioning-scheme: MajorMinorPatchTag
assembly-informational-format: '{InformationalVersion}'
mode: ContinuousDelivery
increment: Patch
continuous-delivery-fallback-tag: ci
tag-prefix: '[vV]'
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
commit-message-incrementing: Enabled
commit-date-format: 'yyyy-MM-dd'
ignore:
  sha: []
merge-message-formats: {}

Thanks for any help.

Hi @KevinLu-MSFT. Apologies for the slow reply. I haven't had a chance to test it yet as a step in the same pipeline previous to this one has stopped working! (different problem) I'll update the answer as soon as I've had a go. Thanks — zXynK
– zXynK, Commented Mar 3, 2021 at 9:51
Thanks for your update. Feel free to let me know if it could help. — Kevin Lu
– Kevin Lu, Commented Mar 3, 2021 at 9:52

mrsauravsahu · Accepted Answer · 2022-08-16 15:15:40Z

7

It seems the FullSemVer is affected: 0.8.0+11

When I use the ContinuousDelivery mode, I could get the same result.

You could try to use the mainline mode in yml file.

Here is my example: You could try to remove the next-version parameter

mode: mainline
tag-prefix: '[vV]'
commit-message-incrementing: Enabled
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)'
assembly-informational-format: '{Major}.{Minor}.{Patch}'

Here is a doc about Gitversion Mainline mode.

Result:

The patch will auto incremente

edited Aug 16, 2022 at 15:15

mrsauravsahu

2,2562 gold badges18 silver badges22 bronze badges

answered Mar 2, 2021 at 8:52

Kevin Lu

36.8k4 gold badges36 silver badges50 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

zXynK Over a year ago

Cheers, looks like it was the mainline bit I had wrong

Collectives™ on Stack Overflow

Why is the patch version not auto incrementing when using GitVersion?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related