chore: add --force-publish to lerna to sync releases #1898
Merged
Conversation
This file contains 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.
Summary:
By default Lerna will only upgrade and publish the packages that were affected by recent changes. However this proves to be tricky, with different CLI sub-packages following different release schedule. To make it less confusing for anyone consuming the packages, this PR adds
--force-publishflag to thelerna publishcommand, so that all packages are synced even when only one was upgraded.This goes in line with the recently added
exactsetting to thelerna.json, which plays better with the way this CLI is consumed by React Native—through exact versions.Test Plan:
Doing it locally and now want to upstream it to the command.