[7.0.x] dotnet nuget why: write target package in graph#6990
Merged
zivkan merged 1 commit intorelease/7.0.xfrom Dec 5, 2025
Merged
[7.0.x] dotnet nuget why: write target package in graph#6990zivkan merged 1 commit intorelease/7.0.xfrom
zivkan merged 1 commit intorelease/7.0.xfrom
Conversation
nkolev92
approved these changes
Dec 5, 2025
Nigusu-Allehu
approved these changes
Dec 5, 2025
marcpopMSFT
approved these changes
Dec 5, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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#14664
Description
Cherry-pick #6975 to the release/7.0.x branch
But without some of the nullable changes, to reduce risk that it could introduce nullable warnings/errors when the dotnet/sdk repo uses it.
PR Checklist
Link to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc..NET approval template:
Customer Impact
Impacts customers using the
dotnet nuget whycommand. 9.0.300 displays a package dependency graph using line characters, with the package names on the same line as the line. 10.0.100 puts the package ID searched for on a new line. There are screenshots in this issue: NuGet/Home#14664Regression?
Risk
Justification: The existing code to draw the package graph was replaced with Spectre.Console.
Addtionally, while another team had already caused Spectre.Console to be included in the upcoming 10.0.200 SDK, it's not currently part of the 10.0.100 SDK. I did validate with the source build team that adding it to 10.0.1xx servicing is acceptable from their point of view
Verification
Packaging changes reviewed?
I'm not sure what exactly is meant by "packaging changes", but as mentioned above, it will cause Spectre.Console.dll to ship in the SDK, which it did not before.