In scenarios where running self-hosted agents in Azure DevOps, and the agents are reused between jobs, later jobs will get the wrong version installed.

• Build agent installs GitVersion with specific version 5.1, in job A.
• After Job A is finished, Job B starts on the same build agent.
• Job B requests GitVersion 5.x, which "5.1" will satisfy, meaning that the job does not get the latest version.

To get around these issues, add an option to the GitVersion install task to always recheck for the latest version.

Detailed Description

How to reproduce:

• Build agent installs GitVersion with specific version 5.1, in job A.
• After Job A is finished, Job B starts on the same build agent.
• Job B requests GitVersion 5.x, which "5.1" will satisfy, meaning that the job does not get the latest version, as Job B would have wanted.

To get around these issues, add an option to the GitVersion install task to always recheck for the latest version.

Context

It reduces issues that happen when an older pipeline has pinned a specific version of GitVersion, but another pipeline wants to have the latest version at all times. In the scenario of re-using agents between jobs.