Repository navigation
Add support for CPM with dotnet package update - #6796
Merged
Merged
Conversation
nkolev92
previously approved these changes
Sep 23, 2025
nkolev92
reviewed
Sep 23, 2025
zivkan
force-pushed
the
dev-zivkan-update-cpm
branch
from
September 30, 2025 03:32
e958b9a to
f1715ad
Compare
donnie-msft
approved these changes
Sep 30, 2025
jeffkl
approved these changes
Sep 30, 2025
nkolev92
approved these changes
Sep 30, 2025
zivkan
added a commit
that referenced
this pull request
Oct 1, 2025
8 of 13 tasks
zivkan
added a commit
that referenced
this pull request
Oct 9, 2025
This was referenced Nov 6, 2025
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
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.
Bug
Fixes: NuGet/Home#14318
Description
dotnet package updateuses the existing helper methods written fordotnet package addto modify project files, and it supports CPM by usingVersionRange.OriginalStringto write the exact string that customers wrote on the command line. However, the constructor forVersionRangecan create instances whereOriginalStringis null. So, useVersionRange.Parseinstead to ensure that OriginalString will always have a value for MSBuildAPIUtility to use.PR Checklist
Link to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc.