Update lerna to the latest version 🚀 #8
Conversation
This file contains 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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 3.0.1 just got published.Update to this version instead 🚀 Release Notesv3.0.1Bug Fixes
|
Version 3.0.2 just got published.Update to this version instead 🚀 Release Notesv3.0.2Bug Fixes
CommitsThe new version differs by 9 commits.
See the full diff |
Version 3.0.3 just got published.Update to this version instead 🚀 Release Notesv3.0.3Bug Fixes |
Version 3.0.4 just got published.Update to this version instead 🚀 Release Notesv3.0.4Bug FixesCommitsThe new version differs by 8 commits.
See the full diff |
Version 3.0.5 just got published.Update to this version instead 🚀 Release Notesv3.0.5Bug Fixes
CommitsThe new version differs by 17 commits.
There are 17 commits in total. See the full diff |
Version 3.0.6 just got published.Update to this version instead 🚀 Release Notesv3.0.6Bug Fixes
CommitsThe new version differs by 13 commits.
See the full diff |
Version 3.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Version 3.1.1 just got published. |
Version 3.1.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
Version 3.2.0 just got published.Update to this version instead 🚀 Release Notesv3.2.0Bug Fixes
Features
CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 3.2.1 just got published.Update to this version instead 🚀 Release Notesv3.2.1Bug Fixes |
Version 3.3.0 just got published.Update to this version instead 🚀 Release Notesv3.3.0Bug Fixes
FeaturesCommitsThe new version differs by 15 commits.
See the full diff |
Version 3.3.1 just got published.Update to this version instead 🚀 Release Notesv3.3.1Bug FixesCommitsThe new version differs by 13 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
🚨 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
|
|
🚨 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
|
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 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 packexperience (627cfc2)Features
@lerna/listableutility (bf56018)npm packbeforenpm publish(8d80b2c)@lerna/log-packedmodule, extracted from npm (9c767ac)lerna versionfrom oflerna publish(#1522) (8b97394),closes #277 #936 #956 #961 #1056 #1118 #1385 #1483 #1494
BREAKING CHANGES
lerna changedlerna lslerna lsno longer shows version strings or private packages.lerna laresembles the old output, with the addition of relative path to the packagelerna llis a shortcut for the new--longoption--parseableoption has been added to aid magical piping incantationslerna publish--preidnow 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-verifyis no longer passed togit commitby default, but controlled by the new--commit-hooksoption: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-hooksto restore the previous behavior.FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴