[rush] Fix an issue where rush add
always adds the latest version if ensureConsistentVersions
is set in rush.json
.
#4828
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.
Summary
Fixes #4826
Details
The code that determines which version to add uses the
ensureConsistentVersions
property from the object that is constructed from thecommon-versions.json
file. This was introduced in #4735. This issue was caused by a missed case - theensureConsistentVersions
property ofrushConfiguration
is marked as@deprecated
, but its value wasn't plumbed into theCommonVersionsConfiguration
object. This PR uses therush.json
value if a value wasn't provided incommon-versions.json
How it was tested
Tested in a repo with a repro, and added unit tests for the
CommonVersionsConfiguration
change.Impacted documentation
None.