You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving forward, nuget.org will be strict and no longer accept packages defining dependencies with an empty version range.
The change to reject empty dependency version ranges is in line with the recommendation as per the docs, which now will be enforced.
For consistent behavior, it's recommended to always specify a version or version range for package dependencies.
Current docs state:
If no version is specified for a dependency, NuGet behaves as follows:
NuGet v2.7.2 and earlier: The latest package version will be used
NuGet v2.8 and later: The lowest package version will be used
I think we should modify this and add:
NuGet v2.8 to v4.1.0: The lowest package version will be used
NuGet v4.3.0 and above: no longer supported and considered an invalid dependency version range
The above of course assumes that NuGet v4.3.0 aligns behavior for pack :) (tracked by NuGet/Home#4985)
The text was updated successfully, but these errors were encountered:
Client pack behavior change is likely only to be part of v4.3.0, so that docs change can wait a little.
Server side change will go live this sprint.
Suggested addition (feel free to reword):
The nuget.org web site no longer accepts packages that declare dependency versions with an empty version range.
By enforcing our earlier recommendation, the nuget.org package validation became a bit more strict, and both service and client became a bit less subject to potential errors caused by illegal dependency version ranges.
skofman1
added a commit
to skofman1/docs.microsoft.com-nuget
that referenced
this issue
Apr 12, 2017
The task is to document the behavioral change in how we validate package dependency version ranges.
Page affected:
https://docs.microsoft.com/en-us/nuget/create-packages/dependency-versions#version-ranges
Moving forward, nuget.org will be strict and no longer accept packages defining dependencies with an empty version range.
The change to reject empty dependency version ranges is in line with the recommendation as per the docs, which now will be enforced.
Current docs state:
I think we should modify this and add:
The above of course assumes that NuGet v4.3.0 aligns behavior for
pack
:) (tracked by NuGet/Home#4985)The text was updated successfully, but these errors were encountered: