[ISSUE]: The version format generated for prerelease builds pre-1.0 are not accepted by NuGet.org.

[otac0n]

Prerequisites

• I have written a descriptive issue title
• I have searched issues to ensure it has not already been reported

GitVersion package

GitVersion.MsBuild

GitVersion version

6.3.0

Operating system

Windows

What are you seeing?

Prerelease versions that aren't tagged as an explicit version generate SemVer versions like 0.0.1-4

While this is valid SemVer 2.0, it is rejected by NuGet.org Please include tag like 0.0.1-build.4 or similar even for prerelease builds.

What is expected?

The version number generated and attached to .nupkg files should never be rejected by NuGet.org.

Steps to Reproduce

Generate a package from a version before 1.0 but do not tag the branch.

RepositoryFixture Test

No response

Output log or link to your CI build (if appropriate).

https://ci.appveyor.com/project/otac0n/conversationmodel/builds/52293368

[HHobeck]

Hi. And what is your suggestion? Like you mentioned it is rather a deficit of nuget.org. Is it not better to create a ticket there? ;) BTW: You can change the label on main any time

[HHobeck]

I think this is related to: #4500 (comment)

Yes, that is also something I have noticed and in my opinion it is a deficit in the design of the semantic version specification. However, because we cannot change it I would suggest either to specify the label to zeta (or better zzz ;)) on main or use the continuous deployment mode (@asbjornu should we change it in the workflow template?). On the GitFlow Examples following is written:

The continuous delivery mode has been used for the main and the support branch in this examples (specified as a fallback on the root configuration layer) to illustrate how the version increments are applied. In production context the continuous deployment mode might be a better option when e.g. the release process is automated or the commits are tagged by the pipeline automatically.

[HHobeck]

If you not mind could you please create a PR and change the mode (on the root level) fromContinuousDelivery to ContinuousDeployment and create new base templates:

• GitFlow (GitFlow/v2)
• GitHubFlow (GitHubFlow/v2)
• TrunkBased (TrunkBased/preview2)

See: https://gitversion.net/docs/reference/configuration

[samsmithnz]

I've read all of the links above, and I admit it's tricky to follow. I think, fundamentally, this breaks versioning in a lot of .NET application, without a clear step forward, especially when publishing to NuGet. I understand the NuGet specification needs to be updated, but that is a bit out of our control.

Is there an easy way to just ignore the prerelease tag and not include it in semver to keep backward compatibility with 5.x?

[HHobeck]

Is there an easy way to just ignore the prerelease tag and not include it in semver to keep backward compatibility with 5.x?

I'm not sure what do you mean with to be backward compatible. Like I mentioned, you can change the label to an arbitrary string or change the mode to continuous deployment.