build: pin transitive NuGet versions centrally - #5
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Enable central transitive NuGet pinning so the existing central package versions also govern transitive dependencies, under WP02.00. Regenerated locks have no semantic changes; all published dependency pins remain unchanged.
Validation: clean-worktree isolated online restore; locked offline repeat against an empty package source; Release build (zero warnings/errors); 89 tests; repository/licence/provenance checks; format verification. An altered central version was rejected with NU1004 and the original graph was restored. Complete one-line diff reviewed. All hosted native/AOT/live checks and post-merge publication verification remain required.