Update npm to the latest version 🚀 #266
Conversation
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 6.0.1 just got published.Update to this version instead 🚀 Release Notesv6.0.1CTRL-C OUT DURING PACKAGE EXTRACTION AS MUCH AS YOU WANT!
SHRONKWRAPS AND LACKFILESIf a published modules had legacy
AUDIT AUDIT EVERYWHEREYou can't use it quite yet, but we do have a few last moment patches to
Looking forwardWe're still a way from having node@11, so now's a good time to ensure we don't warn about being used with it. DOCUMENTATION IMPROVEMENTS
DEPENDENCY UPDATESCommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Version 6.1.0 just got published.Update to this version instead 🚀 Release Notesv6.1.0Look at that! A feature bump! I, for one, have started running it (and the new subcommand...) in all my projects, and it's one of those things that I don't know how I ever functioned -without- it! This will make a world of difference to so many people as far as making the npm ecosystem a higher-quality, safer commons for all of us. This is also a good time to remind y'all that we have a new RFCs repository, along with a new process for them. This repo is open to anyone's RFCs, and has already received some great ideas about where we can take the CLI (and, to a certain extent, the registry). It's a great place to get feedback, and completely replaces feature requests in the main repo, so we won't be accepting feature requests there at all anymore. Check it out if you have something you'd like to suggest, or if you want to keep track of what the future might look like! NEW FEATURE:
|
Version 6.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 58 commits.
There are 58 commits in total. See the full diff |
Version 6.3.0 just got published.Update to this version instead 🚀 Release Notesv6.3.0This is basically the same as the prerelease, but two dependencies have been bumped due to bugs that had been around for a while. CommitsThe new version differs by 21 commits.
There are 21 commits in total. See the full diff |
Version 6.4.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Version 6.4.1 just got published.Update to this version instead 🚀 Release Notesv6.4.1BUGFIXES
DEPENDENCY BUMPS
DOCUMENTATION
CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 42 commits.
There are 42 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 3 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for v6.8.0This release includes an implementation of RFC #10, documenting an optional field that can be used to specify the directory path for a package within a monorepo. NEW FEATURES
BUGFIXES
DEPENDENCY BUMPS
MISCCommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 52 commits ahead by 52, behind by 26.
There are 52 commits in total. See the full diff |
Update to this version instead 🚀 Release Notes for v6.9.1BUGFIXES
DEPENDENCIESCommitsThe new version differs by 12 commits.
See the full diff |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version 6.0.0 of npm was just published.
The version 6.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 npm.
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.
Commits
The new version differs by 121 commits.
7e679fd6.0.073e50a7test: prepublish-only: Use our own copy of npm82dfa546.0.0-next.2408a7ffupdate AUTHORS1b021d0doc: update changelog for [email protected]9c1eb94inflate-shrinkwrap: For git changelings use version as resolved2facb35has-modern-meta: Correctly identify git changelingse4ed976install/deps: Let git deps w/ lock only match package.json552ff6daudit: Ensure we don't mutate the shrinkwrapf2386e1test: standard common-tap1d8ac24test: JSON parse error message changed slightlycd36a21audit: Avoid config-meta's literal-only test09c7348test: Default audit to off when testing8e71334audit: Add docsbe393a2audit: Temporarily suppress git metadata till there's an opt-inThere are 121 commits in total.
See the full diff
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 🌴