Asbjørn Ulsberg

@JakeGinnivan: What SemVer says about this that I can find, is: > Additional **labels** for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format. And: > A...

If no one objects, I'd like to conclude this discussion with renaming `tag` to `label`. PRs welcome. 😃 🙏

This seems simple enough and something we should be able to roll into v5 as it isn't a breaking change. Do you mind changing your target branch to `support/5.x` so...

Meh, unfortunately a lot of tests are failing: ``` Error: unknown test file type for 'artifacts/test-results/GitVersion.MsBuild.Tests.net5.0.results.xml' ``` Have you seen this before, @arturcic?

I seem to be unable to reach the action and YAML. 😕 Can you please download the log from the action and post the YAML as a comment here instead?

Try changing `mode: ContinuousDelivery` to `mode: ContinuousDeployment`. Does that help?

@dxynnez does removing `next-version: 1.0.0` help? You have a quite massive `GitVersion.yml` there. I would even suggest to delete it entirely and just add overrides for whatever you want to...

@bitbonk, yes we are planning to remove most of the legacy version variables and associated configuration properties in v6.

If you don't want padding, can't you use `SemVer` or `FullSemVer`?

`SemVer` and `FullSemVer` follows the [SemVer specification](https://semver.org/), while the various `NuGet…` variables are permutations of `FullSemVer` to fit into old versioning schemes that weren't SemVer compatible. The `.99` syntax is...