This version is covered by your current version range and after updating it in your project the build failed.
As prebuild 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-barebones/branches/greenkeeper-prebuild-6-2-1/builds/1)
Commits
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 6.2.1 of prebuild just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As prebuild 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-barebones/branches/greenkeeper-prebuild-6-2-1/builds/1)Commits
The new version differs by 5 commits.
243dc22
6.2.1
3d4a0d4
Merge pull request #178 from ralphtheninja/master
fb7e89e
Merge pull request #179 from mathiask88/fixTests
4367b9a
fix tests
36a791d
:bug: set gyp.devDir so headers are downloaded correctly
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: