Closed greenkeeper[bot] closed 7 years ago
coveralls
commented
7 years ago Coverage remained the same at 99.422% when pulling 711b0b59aada5c15420a3d50daa6d6a264b46285 on greenkeeper/lerna-2.0.0-rc.1 into 2790053666bbeea0911ba1087c5ea0b34e6775b6 on master.
greenkeeper[bot]
commented
7 years ago Update to this version instead π
The new version differs by 13 commits .
e925c93 2.0.0-rc.208ce858 Update CHANGELOG for v2.0.0-rc.2bed393e Use shell option when spawning lerna exec (#761)b9fa867 Fix durable option resolution (#762)a201362 Use execa for child_process calls (#759)c70af88 Use temp-write for multi-line commit messages (#758)72de558 Use yargs to handle CLI args and subcommands (#719)0e9ec10 Update README.md and docs to better explain hoisting (#751)e0bb584 Reference conventionalcommits.org website in README (#748)607c7a0 Refactor fixture helpers to reduce duplication (#750)614e08a Convert eslint config to YAML (#749)d64f257 Add eslint-plugin-node (#745)d2f4f98 Fix bootstrap integration tests (#747)See the full diff.
greenkeeper[bot]
commented
7 years ago Update to this version instead π
Barring show-stopping bugs, our goal is to cut v2.0.0 later this week. Big props to all of our brave users riding the bleeding edge of release candidates and reporting issues!
lerna bootstrap --npmClient=yarn should no longer require --concurrency=1 to avoid yarn cache race conditions.
If you've ever encountered the error Error: spawn rimraf ENOENT, this should fix that. Turns out yarn doesn't match a behavior of npm when installing, and does not symlink transitive dependency binaries.
The new version differs by 7 commits .
c6a1bef 2.0.0-rc.367addb5 Update CHANGELOG for v2.0.0-rc.33b67f27 chore: trim whitespace in CHANGELOGbb3e740 Resolve internal CLI calls with Windows-safe pattern (#771)83a5e9f Pass multiple directories to rimraf (#770)f96316c Fix custom version prompt (#769)39b9332 Use network mutex when bootstrapping with yarn (#764)See the full diff.
greenkeeper[bot]
commented
7 years ago Update to this version instead π
Now with fewer bugs! The --hoist flag works again, among other rc.3 bugfixes, and our logging is much more detailed now.
npm --global-style. (@ricky)--force-publish arrays and booleans. (@evocateur)The new version differs by 19 commits0.
ef7969f 2.0.0-rc.4ba4f8d7 Update CHANGELOG for v2.0.0-rc.42247fe1 Log the directories being cleaned (#790)b8e7467 Prevent log messages and progress bars from mangling prompts (#787)67543fd appveyor: add --runInBand to yarn run ciaa03b43 Add troubleshooting docs (#783)fbdfa9a Add --max-buffer flag (#782)d16e285 Add tests for npm global style option (#784)bb78176 Support --force-publish arrays and booleans (#781)f9b2ac6 Restore async rimraf loops (#780)e4b461b Log with npmlog (#779)2bcd182 Replace --skip-temp-tag with inverted --temp-tag (#777)6cb677a Fix --hoist with no argument default (#778)c590d57 Always bootstrap non-hoisted leaves using npm --global-style (#775)b72ecb6 Ignore node_modules when traversing nested package locations (#776)There are 19 commits in total.
See the full diff
greenkeeper[bot]
commented
7 years ago Update to this version instead π
This is the last release candidate.
We need to fix #789 before we can release v2.0.0. All contributions are appreciated!
#807 Change exit codes for updated and publish. (@koddsson)
It is now possible to run lerna publish in CI unconditionally, only publishing when changes are actually detected, and never failing when it decides to not publish anything.
Previously:
lerna publish when there are no updates to publish would throw an errorlerna updated when there are no updates would exit 0, making it ineffective as a chained filter (e.g., lerna updated && lerna publish)Now:
lerna publish when there are no updates is a no-op, exiting successfully with a helpful log messagelerna updated when there are no updates will exit non-zero (but not throw an error), enabling it to be an effective filter#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.
lerna exec --only-updated -- ls -la
lerna run --only-updated test#795 Add --parallel flag to lerna exec. (@evocateur)
With this flag, lerna exec will run the command in all filtered packages
in parallel, completely ignoring concurrency and topological sorting.
# transpile modules in all packages as changes occur
lerna exec -- babel src -d lib -w
# transpile watched modules only in package-foo
lerna exec --scope package-foo -- babel src -d lib -wIt 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 watch scripts, with the caveat that concurrency and topological sorting are completely ignored. This is generally the intention when calling lerna run watch and other similar script targets, hence the additional flag.
# the following commands are equivalent
lerna run watch --concurrency=1000 --stream
lerna run watch --parallelPackage filtering (--scope and --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 ls and updated commands. (@ricky)
When run with --json, lerna updated and lerna ls will 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)
node_modules in package paths. (@evocateur)fs-extra. (@evocateur)pkg argument optional for lerna diff. (@evocateur)The new version differs by 18 commits.
31a98aa 2.0.0-rc.526f4056 Update CHANGELOG for v2.0.0-rc5f0b250a Make pkg argument optional for lerna diff (#831)1a8571c Add json output to ls and updated commands (#824)a5ef53d Bump glob (#830)56568d3 Remove '-a' from git tag invocation (#815)20574b0 Prefix piped streams with rotating colors (#829)64203e5 Switch to fs-extra (#828)ce95a26 Upgrade dependencies (#827)880fdf3 Change exit codes for updated and publish (#807)03eb4e9 tweaks [skip ci]22bad8b Add --only-updated option to exec and run subcommands (#726)64a01ac Skip git repo check in commands that do not rely on git (#803)7b72210 Do not ignore explicit node_modules in package paths (#799)bb7cbf3 Disable progress bars when running in CI or non-interactive shell (#798)There are 18 commits in total.
See the full diff
greenkeeper[bot]
commented
7 years ago Update to this version instead π
--canary now bumps the generated version to the next semver minor, and accepts a value (e.g. --canary=beta) to override the default "alpha" tag.lerna run. (@yisraelx)lerna publish --message. (@evocateur)The new version differs by 25 commits.
4f4e99f 2.0.04ccf941 Update CHANGELOG for v2.0.0dc36053 Fix durable option name in README [skip ci]2a302fe Improved canary option functionality (#904)e6d927e Skip update notifiers on CI (#907)616e44c Support Yarn workspaces to replace bootstrap command (#899)80653c7 Clarify warning in hoist.md [skip ci]c1a01a2 Update hoist.md52ad617 Pass extra arguments to npmClient during bootstrap (#834)66e8c02 Add $LERNA_ROOT_PATH env var to lerna exec (#873)a6a3da8 chore(travis): test against node 8 and npm 5 (#861)d24704d fix: shorten error message assert to match npm5 semanticscf11901 Add --since flag to all commands that accept --scope (#822)4f43c3c Allow custom yarn mutex from lerna.json config (#806)3efcd3e Print "MISSING" when a package has no version key. (#857)There are 25 commits in total.
See the full diff
Version 2.0.0-rc.1 of lerna just got published.
The version 2.0.0-rc.1 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.1v2.0.0-rc.1 (2017-04-07)
A silent (but deadly) bug slipped into the last release. Many thanks to (@timdp) for discovering it.
Commits
The new version differs by 94 commits .
d12c4da2.0.0-rc.1c1e7910Update changelog for v2.0.0-rc.1ad7e214Fix package.json updates during publish (#744)634d16dfix: use relative path for file: dependencyf81a9402.0.0-rc.07319e56v2.0.0-rc.0 changelog (#739)25e9b9cUse babel-preset-env (#738)c2fbcb2Update eslint, config, and plugins (#737)c9ed57aCommand: pass explicit CWD to Repository constructor (#734)0cd40ecCommands: pass execOpts to all utility executions to avoid implicit process.cwd() (#733)114a07aUpdate FAQ.md (#736)048d0cbtest(all): Refactor into Jest idioms, adding integration tests (#714)6de5cc5fix(PackageUtilities): remove public API, it's broken anyway (#732)e4b9454fix(BootstrapCommand): symlink binaries of scoped packages correctly (#731)2be31cdUpgrade progress (#729)There are 94 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: