Ensure the yarn.lock file gets updated when publishing #575
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.
Hat tip @anniehu4 for the idea here
Summary:
Currently Lerna doesn't update yarn.lock files when dependencies between monorepo packages increment. See lerna/lerna#1171.
To work around that, we manually install deps during publishing so that the lock file gets updated.
Another workaround would be to use Yarn workspace ranges to specify dependencies between package, so that there's no need to reference specific version numbers.
Unfortunately, Lerna also doesn't support that, either - lerna/lerna#2564.
Test Plan: