[release/9.0.2xx] Update dependencies from nuget/nuget.client #46296
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dotnet-maestro[bot]](https://avatars.githubusercontent.com/in/16706?s=60&v=4){kind=small}
…6.13.1.1 Microsoft.Build.NuGetSdkResolver , NuGet.Build.Tasks , NuGet.Build.Tasks.Console , NuGet.Build.Tasks.Pack , NuGet.CommandLine.XPlat , NuGet.Commands , NuGet.Common , NuGet.Configuration , NuGet.Credentials , NuGet.DependencyResolver.Core , NuGet.Frameworks , NuGet.LibraryModel , NuGet.Localization , NuGet.Packaging , NuGet.ProjectModel , NuGet.Protocol , NuGet.Versioning From Version 6.13.0-rc.113 -> To Version 6.13.1-rc.1
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
This was referenced Jan 25, 2025
|
Approved, but waiting for branding for March's releases before merge. |
…darc-release/9.0.2xx-cbc025dc-be7f-44e3-b778-35550b2d836d
This was referenced Feb 5, 2025
Open
v-wuzhai
approved these changes
Feb 6, 2025
v-wuzhai
deleted the
darc-release/9.0.2xx-cbc025dc-be7f-44e3-b778-35550b2d836d
branch
how was it tested? it doesn't have NuGet/NuGet.Client@20096ab and slnx changes were missed in 9.0.200 |
|
This is the code flow for 9.0.201 next month, where the slnx support is fixed for these two commands |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #40913.
Description
This PR updates the implementation of
dotnet list packageanddotnet whyto support using slnx-formatted solution files as the input arguments. Today those commands only supportslnfiles, which could lead to a user experience cliff if those commands are used in the 9.0.2xx CLI alongside all of the rest of the slnx-related updates we've done to the CLI.Customer Impact
Customers using the 9.0.200 SDK to convert and onboard to slnx support everywhere will not be able to inspect their solutions for outdated packages, or use CLI tooling to discover where a given package or package version is being pulled into their dependency graph.
User-reported
No
Risk
Low - the scope of the change was to two CLI-only commands, no Visual Studio or NuGet.exe experiences are impacted by this change.
Testing
New automated tests were added that verify slnx and sln support for the two commands impacted. In addition, @baronfel did manual testing of the commands on a sample set of slnx-containing repos.
This pull request updates the following dependencies
From https://github.com/nuget/nuget.client