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 Notesv3.0.0
Bug Fixes
add: Always use POSIX paths when computing relative file: specifiers (ffe354f)
add: Support explicit & implicit relative file: specifiers (41f231f)
create: Use filename without scope when generating imports from test file (acfd48b)
The package names emitted to stdout are no longer prefixed by a "- ", and private packages are no longer displayed by default.
lerna ls
The default output of lerna ls no longer shows version strings or private packages.
The new alias lerna la resembles the old output, with the addition of relative path to the package
The new alias lerna ll is a shortcut for the new --long option
A new --parseable option has been added to aid magical piping incantations
lerna 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 to git 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).
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: