Beta tag special treatment

We have a situation like this:

where we had commit on a hotfix branch tagged as 8.2.2-beta.1 and then merged into develop.

for develop we run this: dotnet minver -a minor -d unstable

Expected version: 8.3.0-unstable.1

Actual result: 8.2.2-beta.1.1

Both -a option and -d options are ignore.

[adamralph]

@maxcherednik FYI I raised a PR to add the tagging option to the FAQ — https://github.com/adamralph/minver/pull/352. Thanks for the suggestion.

[adamralph]

@maxcherednik to do that, you would have to first decompose the version. This may be done reliably because the version format is deterministic. I don’t know what language you are using to write your build script, but in C# it’s quite easy:

var metaSplit = version.Split('+', 2);
var preSplit = metaSplit[0].Split('-', 2);
var (rtm, preRelease, buildMetadata) =
    (preSplit[0], preSplit.ElementAtOrDefault(1), metaSplit.ElementAtOrDefault(1));