This version 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 npm.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
This fixes a bug in the metrics reporting where, if you had enabled it then installs would create a metrics reporting process, that would create a metrics reporting process, that would… well, you get the idea. Killing them was tricky because they constantly had new PIDs. There were a few tricks but the easiest was to just reboot.
Anyway, this is a quick release to fix that bug:
51c393f#15237 Don't launch a metrics sender process if we're runnning from a metrics sender process. (@iarna)
Hello lovely humans,
npm just published its new version 4.1.1.
This version 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 npm. 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
v4.1.1 (2016-12-16)
This fixes a bug in the metrics reporting where, if you had enabled it then installs would create a metrics reporting process, that would create a metrics reporting process, that would… well, you get the idea. Killing them was tricky because they constantly had new PIDs. There were a few tricks but the easiest was to just reboot.
Anyway, this is a quick release to fix that bug:
51c393f#15237 Don't launch a metrics sender process if we're runnning from a metrics sender process. (@iarna)The new version differs by 469 commits .
cab7d8a4.1.19cec0d2doc: update changelog for npm@4.1.151c393fmetrics: Don't launch if we're runnning from a sender process5507d584.1.0cc8052cupdate AUTHORSff1f0bbdoc: update changelog for npm@4.1.0650c5fcdoc: rewrite npm doctor docs6749e39code>marked-man@0.2.0</codebea1a2dcode>retry@0.10.1</code57f4bc1code>osenv@0.1.4</code54acc03code>npmlog@4.0.2</code54d949bcode>lockfile@1.0.3</codec2d22facode>nopt@4.0.1</code2359505doctor: add new subcommand0209ee5util: put ansiTrim into util from outdatedThere are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade