fix: publish canary only if lerna detects that packages changed #280
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.
In #276 we forced all packages to be published.
However, when commits do not contain any changes in packages, lerna tries to publish
null
versions.This seems to be a known issue in lerna (lerna/lerna#1769).
This PR attempts to fix that, by triggering the release only if lerna detects that packages have changed. For that, we can use the
lerna changed
command.