[ISSUE]: Gittools Azure DevOps task 3.0.4 unable to retrieve gitversion output variables value or set version

[xlreme]

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?

Platform: Azure DevOps Task
GitTools: 3.0.4
GitVersion: 5.12.0

Unable to output the value for GitVersion.SemVer, GitVersion.NugetVersion and etc in the next subsequent Azure Devops tasks.

This is working in GitTools 3.0.3 and below

What is expected?

The next subsequent Azure DevOps Task should be able to retrieve the GitVersion output values after running gitversion/setup & gitversion/execute tasks.

Steps to Reproduce

1. Use Azure DevOps task gitversion/setup@3 or gitversion/setup@3.0.4, use input, version spec "5.x"

2. Use Azure DevOps task gitversion/execute@3 or gitversion/execute@3.0.4

3. Next, use bash task to output $(Gitversion.SemVer)and note the output.

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

[davidkeaveny]

This issue is related to the change implemented in v3.0.4; there are some further comments there.

[arturcic]

@xlreme you can use $(Gitversion_SemVer) instead https://github.com/GitTools/actions/blob/main/docs/examples/azure/gitversion/execute.md#example-7

[egaudry]

killing of v3.0.4 would allow to restore Azure DevOps service (and possibly others) in no time, is this something we can discuss to mitigate the issue @arturcic @davidkeaveny ?

[Sharparam]

Why was a breaking change released in a patch version?

Edit: Oh I think I misread it as removing /output buildserver from the GitVersion tool itself, but it's just removing it when calling it from the action.

[arturcic]

It should not have been a breaking change, it's a regression, and it should be a minor

[mogrodnv]

Could someone elaborate on the original change? In the PR it just says that "it's duplicating the actions behavior". What does that mean in practical terms?
What is instead expected to happen?

And now as build pipelines are going "boom, boom, boom" all over the world, why hasn't the "3.0.4" version been withdrawn while working on a fix? We're all now implementing workarounds, whether its specifying "@3.0.3" in our YAML pipelines or selecting "2.*" in our classic pipelines (yeah, those still exist..).