Add a "--conservative" flag for "rush generate"#549
Merged
Conversation
… the existing library versions in shrinkwrap.yaml as much as possible. It requires PNPM 1.35.2 with this fix: pnpm/pnpm#1054
Collaborator
Author
|
@sboyleMS @alinsirbu FYI |
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.
Scenario:
package.jsonrush generateNormally this also forces an upgrade of all SemVer range dependencies in shrinkwrap.yaml, which frequently requires the person to fix compatibility issues unrelated to their change.
This is unnecessary for repos that already handle these upgrades automatically in a separate branch. This PR introduces a new switch "--conservative" that causes PNPM to upgrade only the minimal set of dependencies required to satisfy your
package.jsonchanges.NOTE: This change requires pnpm-1.35.2 with the fix for pnpm/pnpm#1054