-
Notifications
You must be signed in to change notification settings - Fork 264
Add dotnet package update command, with --vulnerable option #13961
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mid-way through I realized this was still a WIP, but I finished my review.
hopefully these are helpful.
Happy to chat more as needed.
Co-authored-by: Andy Zivkovic <[email protected]>
Co-authored-by: Andy Zivkovic <[email protected]>
Co-authored-by: Andy Zivkovic <[email protected]>
@NuGet/nuget-client and other interested parties (for example, @baronfel and @richlander), I pushed a significant update to this PR. Please review and provide comments. I want to get this PR merged soon. Keep in mind, it's a feature spec that shows the principals of the new command. It's not a requirement doc that will block implementation pull requests that stray from what's written here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Th
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
No description provided.