Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Invalid package version for nuget.org
-
Hello,
I got Proget Free running with a connector to nuget.org for caching the packages. Now I noticed that there is a problem with the package: Microsoft.Windows.SDK.Win32MetadataWhen trying to download the package version 10.0.19041.5-preview.5 from the ProGet webinterface is returns the http code 400 and the message: Invalid package version was specified.
The issue only seems to affect the web interface and the ODATA (v2) feed. The JSON v3 feed seems to allow to download the package.
The proget version in use is 5.3.22 (Build 10).
Kind regards
Martin
-
Unfortunately this is just an invalid package... someone really needs to tell the developers at Microsoft that the developers at Microsoft really want packages to be in SemVer2 format, per the Microsoft documentation
https://docs.microsoft.com/en-us/nuget/concepts/package-versioning
Microsoft's documentation seems to no longer describe what Microsoft's once documented "legacy versioning" used to be, but we captured it in our documentation before Microsoft removed it.
Bottom line, the "." is an invalid character in a non-SemVer2 (i.e. four-part version number) pre-release tag. Hence, why it's getting a 400 error. It used to do that on NuGet.org, too. I guess it doesn't now. We probably won't change this, since it kind of works already., and since it's only one package.
But if you email the Microsoft team responsible for that package, they probably will just change their versioning going forward. IT'd be nice if Microsoft documented how their non-SemVer2 packages are supposed to work.
