An in-range update of node-libs-browser is breaking the build 🚨
greenkeeper opened this issue · 1 comments
Version 1.0.0 of node-libs-browser just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | node-libs-browser |
| Current Version | 0.6.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As node-libs-browser 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
- ❌ ci/circleci Your tests failed on CircleCI Details
Commits
The new version differs by 4 commits (ahead by 4, behind by 3).
-
a6cef601.0.0 -
371b183updated dependencies -
a3a3a7dMerge pull request #36 from philikon/latest_crypto -
1cb2c8aUpgrade crypto-browserify dependency to latest 3.10.0
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 0.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.