Open greenkeeper[bot] opened 6 years ago
devDependency
lerna was updated from 2.11.0
to 3.16.1
.devDependency
lerna was updated from 2.11.0
to 3.16.2
.devDependency
lerna was updated from 2.11.0
to 3.16.3
.devDependency
lerna was updated from 2.11.0
to 3.16.4
.devDependency
lerna was updated from 2.11.0
to 3.16.5
.devDependency
lerna was updated from 2.11.0
to 3.17.0
.devDependency
lerna was updated from 2.11.0
to 3.18.0
.devDependency
lerna was updated from 2.11.0
to 3.18.1
.devDependency
lerna was updated from 2.11.0
to 3.18.2
.devDependency
lerna was updated from 2.11.0
to 3.18.3
.devDependency
lerna was updated from 2.11.0
to 3.18.4
.devDependency
lerna was updated from 2.11.0
to 3.18.5
.devDependency
lerna was updated from 2.11.0
to 3.19.0
.devDependency
lerna was updated from 2.11.0
to 3.20.0
.devDependency
lerna was updated from 2.11.0
to 3.20.1
.π¨ Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! π ππ¨ π
Find out how to migrate to Snyk at greenkeeper.io
devDependency
lerna was updated from 2.11.0
to 3.21.0
.π¨ Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! π ππ¨ π
Find out how to migrate to Snyk at greenkeeper.io
devDependency
lerna was updated from 2.11.0
to 3.22.0
.
Version 3.0.0 of lerna was just published.
The version 3.0.0 is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of lerna.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donβt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v3.0.0Bug Fixes
file:
specifiers (ffe354f)file:
specifiers (41f231f)npm pack
experience (627cfc2)Features
@lerna/listable
utility (bf56018)npm pack
beforenpm publish
(8d80b2c)@lerna/log-packed
module, extracted from npm (9c767ac)lerna version
from oflerna publish
(#1522) (8b97394),closes #277 #936 #956 #961 #1056 #1118 #1385 #1483 #1494
BREAKING CHANGES
lerna changed
lerna ls
lerna ls
no longer shows version strings or private packages.lerna la
resembles the old output, with the addition of relative path to the packagelerna ll
is a shortcut for the new--long
option--parseable
option has been added to aid magical piping incantationslerna publish
--preid
now defaults to "alpha" during prereleases:The previous default for this option was undefined, which led to an awkward "1.0.1-0" result when passed to
semver.inc()
.The new default "alpha" yields a much more useful "1.0.1-alpha.0" result. Any previous prerelease ID will be preserved, justas it was before.
--no-verify
is no longer passed togit commit
by default, but controlled by the new--commit-hooks
option:The previous behavior was too overzealous, and the new option operates exactly like the corresponding npm version option of the same name.
As long as your pre-commit hooks are properly scoped to ignore changes in package.json files, this change should not affect you. If that is not the case, you may pass
--no-commit-hooks
to restore the previous behavior.FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: