Update lerna to the latest version 🚀 #915
Merged
Conversation
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
ndelangen
approved these changes
Apr 23, 2017
This was referenced Jan 22, 2020
|
View your CI Pipeline Execution ↗ for commit 07be80d.
☁️ Nx Cloud last updated this comment at |
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.
Version 2.0.0-rc.3 of lerna just got published.
The version 2.0.0-rc.3 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of lerna.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v2.0.0-rc.3v2.0.0-rc.3 (2017-04-18)
Barring show-stopping bugs, our goal is to cut
v2.0.0later this week. Big props to all of our brave users riding the bleeding edge of release candidates and reporting issues!🐛 Bug Fix
lerna bootstrap --npmClient=yarnshould no longer require--concurrency=1to avoid yarn cache race conditions.If you've ever encountered the error
Error: spawn rimraf ENOENT, this should fix that. Turns outyarndoesn't match a behavior ofnpmwhen installing, and does not symlink transitive dependency binaries.🏠 Internal
Committers: 2
Commits
The new version differs by 7 commits .
c6a1bef2.0.0-rc.367addb5Update CHANGELOG for v2.0.0-rc.33b67f27chore: trim whitespace in CHANGELOGbb3e740Resolve internal CLI calls with Windows-safe pattern (#771)83a5e9fPass multiple directories to rimraf (#770)f96316cFix custom version prompt (#769)39b9332Use network mutex when bootstrapping with yarn (#764)See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴