This pull request introduces a new configuration option for Azure Pipeline task: buildNumberFormat option which allows to specify the build number format.

Example:

steps:
  # gitversion/setup@3.2.1 task omitted for brevity.

  - task: gitversion/execute@3.2.1
    displayName: Determine Version
    name: version_step # step id used as a reference for output values
    inputs:
      buildNumberFormat: 'v${GitVersion_MajorMinorPatch}' # or 'v$GitVersion_MajorMinorPatch' 

Closes #1434
Closes #1493

Configuration Updates:

• .azure/ci.yml, .github/workflows/ci.yml, and other YAML files: Replaced update-build-number=false with semantic-version-format=Loose and added the buildNumberFormat input to support custom build number formatting. [1] [2]

Documentation Updates:

• docs/examples/azure/gitversion/execute.md and docs/examples/github/gitversion/execute.md: Updated examples to reflect the new semantic-version-format configuration and added documentation for the buildNumberFormat option. Examples were renamed for clarity (e.g., "Example 8" to "Output Example 1"). [1] [2] [3]

Test Enhancements:

• src/__tests__/tools/gitversion/runner.spec.ts: Added tests for the new buildNumberFormat option, including mocking and validation of updateBuildNumber behavior. Improved assertions to check for stdout and stderr. [1] [2]
• src/__tests__/tools/gitversion/settings.spec.ts: Updated tests to validate the semantic-version-format and buildNumberFormat settings. Refactored variable names for consistency. [1] [2]