[Improvement] Don't consider `tag-prefix` as optional

[AlexPykavy]

Detailed Description

Currently tag-prefix is always considered as optional which makes calculation of the next version incorrect. It mixes prefixed and unprefixed versions and takes the largest of both.

Context

To correctly calculate the next version with the prefix. For example, we develop the main product and some its plugin in the same repository and have the following git tags list:

• 0.1.0
• 0.1.1
• 0.2.0
• 0.2.1
• plugin_0.1.0
• plugin_0.1.1
  The expected next plugin version is 0.1.2 not 0.2.2 (plugin_ prefix will be prepended before setting the tag).

Possible Implementation

[arturcic]

Fixed by #3208

[andyfurniss4]

Is this available for use yet? If not, do you know when the next release is planned for?

I've also encountered this issue where I am trying to use GitVersion in a repo that already has a bunch of non-prefixed tags used for other things. I want my GitVersion-ing to be independent of these other tags. I need the tag-prefix to be enforced rather than optional so I can ignore all the older tags and only focus on new tags prefixed with whatever I want to prefix with.

[asbjornu]

This will be a part of our next release of v5, @andyfurniss4. We haven't planned one yet, but we do them fairly regularly.

[andyfurniss4]

Thanks @asbjornu

[arturcic]

🎉 This issue has been resolved in version 5.11.0 🎉
The release is available on:

• GitHub Release
• Chocolatey Package
• .Net Global Tool

Your GitReleaseManager bot 📦🚀