Details
-
Type:
Bug
-
Status: New
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.28.1
-
Fix Version/s: None
-
Labels:
-
Notability:4
Description
Publish the package https://www.nuget.org/packages/Microsoft.Web.Infrastructure/1.0.0 into a nuget hosted repo in NXRM.
Then configure visual studio to use that hosted repo as a source.
When looking up the package, we see this:
The version displays as 1.0.0.0 ( non-normalized )
Compare this with the same package hosted at NuGet.org:
The version displays as 1.0.0 ( normalized )
Or via an NXRM proxy repo to nuget.org V3 API endpoint:
The version displays as 1.0.0 ( normalized )
Expected
Act like NuGet.org, render package versions to NuGet clients using V3 API in their normalized form, even if the published package contains a non-normalized version.
A group repo with hosted and proxy should show normalized versions without build information
check an URL like
http://localhost:8081/repository/nuget-group/v3/registration/5/nuget.commandline/index.json
the lower and upper version as well as the items should show a normalized version (a version without build information)
4.4.2+c2b552fbc4ba50b477fc5680790b1b06fef629c2 would be a non normalized version
4.4.2 would be a normalized version
Attachments
Issue Links
- is related to
-
NEXUS-25908 nuget restore does not resolve inbound normalized package versions to unnormalized published versions using NuGet v3
-
- Closed
-