An in-range update of prebuild is breaking the build 🚨
greenkeeper opened this issue · 2 comments
Version 6.2.1 of prebuild just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | prebuild |
| Current Version | 6.2.0 |
| Type | devDependency |
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 💪
Status Details
- ❌ semaphoreci The build failed on Semaphore. Details
Commits
The new version differs by 5 commits.
243dc226.2.13d4a0d4Merge pull request #178 from ralphtheninja/masterfb7e89eMerge pull request #179 from mathiask88/fixTests4367b9afix tests36a791d: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 and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
After pinning to 6.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 6.2.2 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀