-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update NuGet Packages #2690
Update NuGet Packages #2690
Conversation
Usually, we update package reference versions only when we need to (i.e. vulnerability detected, compliance issue, need new version for new feature, out of support, etc). And we "try" to make all projects point to same package version to minimize potential issues. Since this one mostly only affects tests and projects that are not used in other places(except the wingetutilinterop which is used in winget service), I think it's probably ok if the wingetutilinterop change is reverted. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
As far as I could tell, these changes don't cause any build issues. But, knowing my luck, I'm probably missing something. Lets just see where this lands.
This doesn't update all NuGet packages, just the ones that seemed like they were close in version and were unlikely to have breaking changes.
Microsoft Reviewers: Open in CodeFlow