Update lerna to the latest version 🚀#1101
Merged
Conversation
ndelangen
approved these changes
May 23, 2017
Member
|
I will test this locally before merging |
Codecov Report
@@ Coverage Diff @@
## master #1101 +/- ##
=========================================
Coverage ? 12.73%
=========================================
Files ? 199
Lines ? 4475
Branches ? 711
=========================================
Hits ? 570
Misses ? 3275
Partials ? 630
Continue to review full report at Codecov.
|
|
View your CI Pipeline Execution ↗ for commit a593145
☁️ Nx Cloud last updated this comment at |
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
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.5 of lerna just got published.
The version 2.0.0-rc.5 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.5v2.0.0-rc.5 (2017-05-22)
This is the last release candidate.
We need to fix #789 before we can release
v2.0.0. All contributions are appreciated!💥 Breaking Change
#807 Change exit codes for
updatedandpublish. (@koddsson)It is now possible to run
lerna publishin CI unconditionally, only publishing when changes are actually detected, and never failing when it decides to not publish anything.Previously:
lerna publishwhen there are no updates to publish would throw an errorlerna updatedwhen there are no updates wouldexit 0, making it ineffective as a chained filter (e.g.,lerna updated && lerna publish)Now:
lerna publishwhen there are no updates is a no-op, exiting successfully with a helpful log messagelerna updatedwhen there are no updates will exit non-zero (but not throw an error), enabling it to be an effective filter🚀 Enhancement
#726 Add --only-updated option to exec and run subcommands. (@jameslnewell)
When executing a script or command, only run the script or command on packages that have been updated since the last release. A package is considered "updated" using the same rules as
lerna updated.#795 Add --parallel flag to
lerna exec. (@evocateur)With this flag,
lerna execwill run the command in all filtered packagesin parallel, completely ignoring concurrency and topological sorting.
It is advised to constrain the scope of the command when running with this
flag, as spawning dozens of subprocesses may be harmful to your shell's
equanimity (or maximum file descriptor limit, for example). YMMV
#796 Add --parallel flag to
lerna run. (@evocateur)This allows simpler invocation of
watchscripts, with the caveat that concurrency and topological sorting are completely ignored. This is generally the intention when callinglerna run watchand other similar script targets, hence the additional flag.# the following commands are equivalent lerna run watch --concurrency=1000 --stream lerna run watch --parallelPackage filtering (
--scopeand--ignore) is still available when this new flag is being used, and it is advised to narrow the scope of parallel execution when you have more than a dozen packages or so (YMMV).#803 Skip git repo check by default in Commands which do not rely on git. (@noherczeg)
#824 Add json output to
lsandupdatedcommands. (@ricky)When run with
--json,lerna updatedandlerna lswill return an array of objects in the following format:[ { "name": "package", "version": "1.0.0", "private": false } ]#829 Prefix piped streams with rotating colors. (@evocateur)
🐛 Bug Fix
node_modulesin package paths. (@evocateur)fs-extra. (@evocateur)pkgargument optional forlerna diff. (@evocateur)🏠 Internal
Committers: 6
Commits
The new version differs by 18 commits.
31a98aa2.0.0-rc.526f4056Update CHANGELOG for v2.0.0-rc5f0b250aMake pkg argument optional for lerna diff (#831)1a8571cAdd json output tolsandupdatedcommands (#824)a5ef53dBump glob (#830)56568d3Remove '-a' from git tag invocation (#815)20574b0Prefix piped streams with rotating colors (#829)64203e5Switch to fs-extra (#828)ce95a26Upgrade dependencies (#827)880fdf3Change exit codes forupdatedandpublish(#807)03eb4e9tweaks [skip ci]22bad8bAdd --only-updated option to exec and run subcommands (#726)64a01acSkip git repo check in commands that do not rely on git (#803)7b72210Do not ignore explicit node_modules in package paths (#799)bb7cbf3Disable progress bars when running in CI or non-interactive shell (#798)There are 18 commits in total.
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 🌴