This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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 covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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 42 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 42 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade