include old version number whenever possible #12962
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
1 task
JamieMagee
previously approved these changes
Aug 27, 2025
brettfo
force-pushed
the
dev/brettfo/nuget-directory-glob
branch
from
0be1dde to
854447b
Compare
brettfo
force-pushed
the
dev/brettfo/nuget-directory-glob
branch
from
854447b to
a2510a8
Compare
JamieMagee
approved these changes
Aug 27, 2025
This was referenced Aug 27, 2025
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.
When generating a PR title, the old version number is mentioned if only a single version update was performed. If the same update was performed in multiple directories, however, this didn't happen.
The fix is to get the distinct set of old and new version numbers and only then see if it's appropriate to mention the old version number.
Swift smoke test failure due to #12647.