Add vulnerable option to dotnet list package #14352
Merged
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.
This is a cherry-pick of the commit from #13318 into release/5.0.2xx. Details copied below:
Added
--vulnerable
option todotnet list package
CLI. Also removed most of the "policing" around other option combinations:--include-prerelease
,--highest-minor
, andhighest-patch
are only supposed to be used in combination with the--outdated
option, but they're just ignored by the NuGet Xplat CLI otherwise, and we'll do the same here.--config
and--source
are only supposed to be used in combination with--vulnerable
,--outdated
and--deprecated
reports, but they're also just ignored by the NuGet Xplat CLI, so we'll ignore them here.--vulnerable
,--outdated
and--deprecated
all must be used mutually exclusively, and combining them is nonsense--we throw in the NuGet Xplat CLI in this case, and we'll continue to throw here.