Don't select transitive packages in PM UI when updating a package #6179
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.
Bug
Fixes: NuGet/Home#13893
Description
Transitive packages are automatically selected when you are in the Updates tab and clicking the Update button will update the package reference for the top-level packages but also add a package reference in all the projects where the package is used as a transitive dependency, promoting them to top-level, which is not the desired behavior in most of the cases.
Promoting a package from transitive to top-level is not a very common scenario, most likely only done when fixing a vulnerability or resolving a dependency conflict.
PR Checklist
I'm not adding since it's a UI change in a code path with no tests, I could try to add a unit test if team wants