dotnet nuget why: write target package in graph #6975
Merged
Conversation
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
zivkan
commented
Dec 3, 2025
jeffkl
approved these changes
Dec 3, 2025
martinrrm
approved these changes
Dec 3, 2025
zivkan
added a commit
that referenced
this pull request
Dec 4, 2025
|
What version will this be available in and in which version of the .NET 10 SDK? Could it be backported to 10.0.1xx? |
13 tasks
This was referenced Dec 5, 2025
zivkan
added a commit
that referenced
this pull request
Dec 5, 2025
Member
Author
|
It was backported. It should make it in the 10.0.102 SDK. |
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.
Bug
Fixes: NuGet/Home#14664
Description
Fix
dotnet nuget why's output, by porting the custom colour output logger to Spectre.Console.This PR depends on the following two PRs being merged into .NET:
If they're not merged, then I just need to download the package version in this PR, but the test package has additional dependencies, so it will require additional package source mappings.
There's a very minor output difference, our custom outputter was putting an "empty line" between the TFM and the first package, whereas Spectre.Console doesn't.
Previous why implementation:
Spectre.Console (this PR):
PR Checklist
Link to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc.