GitVersion icon indicating copy to clipboard operation
GitVersion copied to clipboard

[ISSUE]: Unable to Bump Up Major Version

Open juicybaba opened this issue 1 year ago • 0 comments

Prerequisites

  • [X] I have written a descriptive issue title
  • [X] I have searched issues to ensure it has not already been reported

GitVersion package

AzureDevops task

GitVersion version

5.12

Operating system

Linux

What are you seeing?

Creating a dedicated issue for Q2 in #3939

Add +semver: breaking or +semver: major in commit message bump up minor instead of major version. I am using default config, there is no local config file. minor and patch version can be bumped with the required message as expected.

steps:
  - checkout: self
    fetchDepth: 0
    persistCredentials: true
  - task: gitversion/setup@0
    inputs:
      versionSpec: '5.x'
  - task: gitversion/execute@0
    name: version
  - script: |
      echo "Major: $(version.major)"
      echo "Minor: $(version.minor)"
      echo "Patch: $(version.patch)"
      echo "PreReleaseTag: $(version.preReleaseTag)"
      echo "PreReleaseTagWithDash: $(version.preReleaseTagWithDash)"
      echo "PreReleaseLabel: $(version.preReleaseLabel)"
      echo "PreReleaseNumber: $(version.preReleaseNumber)"
      echo "WeightedPreReleaseNumber: $(version.weightedPreReleaseNumber)"
      echo "BuildMetaData: $(version.buildMetaData)"
      echo "BuildMetaDataPadded: $(version.buildMetaDataPadded)"
      echo "FullBuildMetaData: $(version.fullBuildMetaData)"
      echo "MajorMinorPatch: $(version.majorMinorPatch)"
      echo "SemVer: $(version.semVer)"
      echo "LegacySemVer: $(version.legacySemVer)"
      echo "LegacySemVerPadded: $(version.legacySemVerPadded)"
      echo "AssemblySemVer: $(version.assemblySemVer)"
      echo "AssemblySemFileVer: $(version.assemblySemFileVer)"
      echo "FullSemVer: $(version.fullSemVer)"
      echo "InformationalVersion: $(version.informationalVersion)"
      echo "BranchName: $(version.branchName)"
      echo "EscapedBranchName: $(version.escapedBranchName)"
      echo "Sha: $(version.sha)"
      echo "ShortSha: $(version.shortSha)"
      echo "NuGetVersionV2: $(version.nuGetVersionV2)"
      echo "NuGetVersion: $(version.nuGetVersion)"
      echo "NuGetPreReleaseTagV2: $(version.nuGetPreReleaseTagV2)"
      echo "NuGetPreReleaseTag: $(version.nuGetPreReleaseTag)"
      echo "VersionSourceSha: $(version.versionSourceSha)"
      echo "CommitsSinceVersionSource: $(version.commitsSinceVersionSource)"
      echo "CommitsSinceVersionSourcePadded: $(version.commitsSinceVersionSourcePadded)"
      echo "UncommittedChanges: $(version.uncommittedChanges)"
      echo "CommitDate: $(version.commitDate)"
  - script: |
      git tag v$(version.MajorMinorPatch)
      git push origin v$(version.MajorMinorPatch)
      git tag -f v$(version.Major)
      git push origin -f v$(version.Major)

What is expected?

Major version can be bumped as expected.

Steps to Reproduce

setup gitversion in azure devops task without customized config and add +semver: breaking or +semver: major in commit message

RepositoryFixture Test

No response

Output log or link to your CI build (if appropriate).

No response

juicybaba avatar Mar 03 '24 15:03 juicybaba