Semantic Versioning 2.0.0

When can we expect support for Semantic versioning 2.0.0 ?

When publishing a package that has version number that follows semver 2.0.0 it fails with the fallowing error:

"System.Net.Http.HttpRequestException: Response status code does not indicate success: 500 (There was an error processing the request: Invalid version number.)."

Product: ProGet
Version: 4.3.1

ProGet already supports SemVer2 for Universal Packages.

Unfortunately, NuGet does not yet support this. Remember they also have a "quasi-support" for this quirky 4-party version number as well, which so many packages utilize.

Please refer to the NuGet Team's documentation on SemVer.

3.0.0 and up support SemVer 2.0.0 with a limited capacity. Local folders and shares are unable to parse versions with multiple release labels or metadata due to the use of NuGet.Core.dll from the older 2.11.0 client.
Project.json restore supports SemVer 2.0.0 and is able to read local folders correctly since it does not depend on NuGet.Core.dll. In some scenarios metadata is written to the disk folder path which causes. Multiple release labels are supported.
Starting in NuGet Client 3.5.0-rc1 has added SemVer 2.0.0 for supported for local folders and UNC shares.

It's a much more complicated issue than it appears at first, and with the velocity of the NuGet team's releases has slowed, and it's likely NuGet will not fully support this in a while (document was from Oct 2016).

We may add some support for this down the line, but it would require a major change to the way we do package indexing, and thus could impact a lot of our enterprise customers. You ought to consider changing your requirement if you're going to use NuGet packages, given the limited supported from the NuGet team for it.