This version is covered by your current version range and after updating it in your project the build failed.
As npm is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/nodeos/nodeos-usersfs/branches/greenkeeper-npm-4-6-1/builds/1)
Release Notesv4.6.1
v4.6.1 (2017-04-21)
A little release to tide you over while we hammer out the last bits for npm@5.
FEATURES
d13c9b2f2init-package-json@1.10.0: The name: prompt is now package name: to make this less ambiguous for new users.
The default package name is now a valid package name. For example: If your package directory has mixed case, the default package name will be all lower case.
f08c66323#16213 Add --allow-same-version option to npm version so that you can use npm version to run your version lifecycles and tag your git repo without actually changing the version number in your package.json. (@lucastheisen)
f5e8becd0 Timing has been added throughout the install implementation. You can see it by running a command with --loglevel=timing. You can also run commands with --timing which will write an npm-debug.log even on success and add an entry to _timing.json in your cache with the timing information from that run. (@iarna)
BUG FIXES
9c860f2ed#16021 Fix a crash in npm doctor when used with a registry that does not support the ping API endpoint. (@watilde)
65b9943e9#16364 Shorten the ELIFECYCLE error message. The shorter error message should make it much easier to discern the actual cause of the error. (@j-f1)
a87a4a835npmlog@4.0.2: Fix flashing of the progress bar when your terminal is very narrow. (@iarna)
41c10974fwrite-file-atomic@1.3.2: Wait for fsync to complete before considering our file written to disk. This will improve certain sorts of Windows diagnostic problems.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 4.6.1 of npm just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As npm is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/nodeos/nodeos-usersfs/branches/greenkeeper-npm-4-6-1/builds/1)Release Notes
v4.6.1v4.6.1 (2017-04-21)
A little release to tide you over while we hammer out the last bits for npm@5.
FEATURES
d13c9b2f2init-package-json@1.10.0: Thename:prompt is nowpackage name:to make this less ambiguous for new users.The default package name is now a valid package name. For example: If your package directory has mixed case, the default package name will be all lower case.
f08c66323#16213 Add--allow-same-versionoption tonpm versionso that you can usenpm versionto run your version lifecycles and tag your git repo without actually changing the version number in yourpackage.json. (@lucastheisen)f5e8becd0Timing has been added throughout the install implementation. You can see it by running a command with--loglevel=timing. You can also run commands with--timingwhich will write annpm-debug.logeven on success and add an entry to_timing.jsonin your cache with the timing information from that run. (@iarna)BUG FIXES
9c860f2ed#16021 Fix a crash innpm doctorwhen used with a registry that does not support thepingAPI endpoint. (@watilde)65b9943e9#16364 Shorten the ELIFECYCLE error message. The shorter error message should make it much easier to discern the actual cause of the error. (@j-f1)a87a4a835npmlog@4.0.2: Fix flashing of the progress bar when your terminal is very narrow. (@iarna)41c10974fwrite-file-atomic@1.3.2: Wait forfsyncto complete before considering our file written to disk. This will improve certain sorts of Windows diagnostic problems.2afa9240c#16336 Don't ham-it-up when expecting JSON. (@bdukes)DOCUMENTATION FIXES
566f3eebe#16296 Use a single convention when referring to the<command>you're running. (@desfero)ccbb94934#16267 Fix a missing space in the example package.json. (@famousgarkin)DEPENDENCY UPDATES
ebde4ea33hosted-git-info@2.4.2c46ad71bbinit-package-json@1.9.6d856d570dnpm-registry-client@8.1.14a2e14436readable-stream@2.2.9f0399138enormalize-package-data@2.3.8Commits
The new version differs by 4 commits0.
3fb3f724.6.19abd882doc: changelog for 4.6.1afa7c03write-file-atomic@1.3.34d833afinit-package-json@1.10.1false
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: