Update lerna from 2.2.0 to 2.3.1 in / #1954
Merged
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.
lerna has been updated to 2.3.1 in / by dependencies.io
2.3.1
This is what happens when you forget to pull from upstream before publishing.
💅 Polish
Committers: 1
2.3.0
New options for
lerna import
andlerna publish
, set--loglevel
from lerna.json, and more!🚀 Enhancement
--flatten
option to use when merge conflicts cannot be imported. (dmaksimovic)--allow-branch
option to restrict publish to designated branches. (FaHeymann)🐛 Bug Fix
--canary=<value>
as prerelease tag, not commit-ish. (achingbrain)--loglevel
config from lerna.json. (evocateur)📝 Documentation
🏠 Internal
npmPublishAsPrerelease
tonpmPublish
to avoid confusion. (Hypnosphi)Committers: 7