Prerequisites

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

GitVersion package

AzureDevops task

What are you seeing?

I tested the GitVersion task 4.0.0 on my Azure DevOps pipeline and I found the following issues:

• I had to change my config to explicitly add the the configFilePath argument to GitVersion.yml. Otherwise I got an error that no config could be found.
  I think it's because there's no default anymore, see https://github.com/GitTools/actions/blob/bc13e9b30988f63de67566813c2036aa81201db4/gitversion/execute/action.yml#L27C1-L29C20

• The version of the build was also not adjusted in Azure DevOps. When reading the docs I notice this is the default new behaviour, but I didn't spot it as a breaking change at first.
  

This is my new config:

  jobs:
  - job: Version
    displayName: 'Determine version'
  
    pool:
      vmImage: 'ubuntu-latest'
  
    steps:
    - checkout: self
      fetchDepth: 0

    - task: gitversion/setup@4.0.0
      displayName: 'Install GitVersion'
      inputs:
        versionSpec: '6.3.x'

    - task: gitversion/execute@4.0.0
      displayName: 'Determine application version with GitVersion'
      name: version_step # step id used as reference for output values
      inputs:
        configFilePath: 'GitVersion.yml'
        buildNumberFormat: '${GitVersion_FullSemVer}'

This is my old config:

  jobs:
  - job: Version
    displayName: 'Determine version'
  
    pool:
      vmImage: 'ubuntu-latest'
  
    steps:
    - checkout: self
      fetchDepth: 0

    - task: gitversion/setup@3.2.1
      displayName: 'Install GitVersion'
      inputs:
        versionSpec: '6.3.x'

    - task: gitversion/execute@3.2.1
      displayName: 'Determine application version with GitVersion'
      name: version_step # step id used as reference for output values

What is expected?

• Find the GitVersion.yml without setting it explicitly via configFilePath or adjust the docs to make it clear that it's a required field
• Adjust the release docs to mention that setting the buildNumberFormat is required and that to keep compatibility with v3, you should add buildNumberFormat: '${GitVersion_FullSemVer}'

Steps to Reproduce

.

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