Policy change for the NuGet CLI version included in the sdk images #928
MichaelSimons
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Policy change for the NuGet CLI version included in the sdk images
We are announcing a policy change for which NuGet CLI (i.e. NuGet.exe) version is included in the sdk images. The plan is to align the NuGet CLI version with the version of NuGet bundled within MSBuild and the .NET CLI included in the sdk images.
If you are using the NuGet CLI you may be impacted by this change. If you are using NuGet via MSBuild or the .NET CLI you will not be affected by this change.
Details
Current Policy
The NuGet CLI version varies for each version of Windows. The included NuGet CLI version is the most recent version at the time of the intial Windows release. The NuGet CLI does get patch updates as they are released.
We originally chose this policy because we thought it was the lowest risk of introducing breaking changes. The current policy however causes compatibility issues. In order to maintain compatibility between the NuGet CLI, MSBuild and the .NET CLI, the versions need to be the same. Examples of these compatibility issues include:
New Policy
Align the NuGet CLI version with with the version of NuGet bundled within MSBuild and the .NET CLI. The version of NuGet included in MSBuild and the .NET CLI is upgraded overtime as VS is serviced. Therefore the NuGet CLI version will also get upgraded over time.
Migration Plan
In an effort to limit the impact to users, we will upgrade the NuGet CLI in a phased approach.
Beta Was this translation helpful? Give feedback.
All reactions