Allow tags with the format v1.0 or v1.1

[cmenzi]

Allow tags with the format v1.0 or v1.1

[adamralph]

@cmenzi thank you for raising this. By design, MinVer does, indeed, only support valid SemVer 2.0 versions. And, as you say, 1.0 is not a valid SemVer 2.0 version. My concern with adding support for this is two-fold:

• SemVer only supports one way of expressing a valid SemVer version. That is, I can only express 1.0.0 in one way. With that exact string. If we introduce automatic conversion of invalid versions, then we will have at least two ways of expressing 1.0.0: both 1.0.0 and 1.0. What if MinVer finds one on one branch, and one on the other? Which is right? It might be 1.0.0 in some contexts, and 1.0 in others. Sure, we could make the conversion configurable, allowing disabling/enabling, or allow configuration of precedence, but as we add all these things, complexity grows.
• This is one example, but what other invalid SemVer versions might people start requesting support for?

These points make me reluctant to add support for this.

But let's explore your listed alternative:

Retag the whole git history of 400+ gitlab projects.

A script could probably do this fairly quickly. How about writing that script? You can run it once and then your'e done. And no complexity has been added to MinVer.

[adamralph]

I will also try what it means if we just add the additional tag with the correct version.

As far as MinVer is concerned, that will be fine, because it will just continue to ignore the invalid (non-SemVer) tags.

I guess minver will take last good candidate.

Exactly. The presence of the older invalid (non-SemVer) tags makes no difference to how MinVer calculates the version.

[cmenzi]

Thank you for the response.

We we really did our tagging concept without bad intentions, because of GitVersion handled this from beginning. Like the tag v1.0 implicitly produced 1.0.0 and from then on, the Patch part was incremented automatically.

I can also understand that you would like to be strict here, as it's an official specification.

I think a script could do it. Just need to ensure that no build is triggered, which should be possible. I will also try what it means if we just add the additional tag with the correct version.

Another option could also be, that we just start now with correct tagging. I guess minver will take last good candidate.

[adamralph]

@cmenzi assuming you're pursuing one of the alternative paths we've discussed, I'm closing this for now. Feel free to re-open if required.