Enable transitive pinning for central package management#6225
Merged
Conversation
JohnMcPMS
approved these changes
May 13, 2026
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
2 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.
📖 Description
This PR enables transitive pinning for central NuGet package management. This makes the version declared in
Directory.Packages.propsapply to transitive dependencies, without having to add them as direct dependencies of a project.This solves a CG alert about
System.Security.Cryptography.XmlinAppInstallerCLIE2ETests.csproj.I'm also removing references that I believe were there only to pin their version with CPM
🔗 References
https://learn.microsoft.com/nuget/consume-packages/central-package-management#transitive-pinning
🔍 Validation
Fully untested because a VS update left me unable to build the project :-)
✅ Checklist
📋 Issue Type
Microsoft Reviewers: Open in CodeFlow