An in-range update of babel-cli is breaking the build 🚨
greenkeeper opened this issue · comments
Version 6.22.0 of babel-cli just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-cli |
| Current Version | 6.18.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-cli 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
-
✅ bitHound - Code No failing files. Details
-
❌ bitHound - Dependencies 1 failing dependency. Details
-
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
-
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
-
✅ codecov/patch Coverage not affected when comparing f651e9d...e7f2d95 Details
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.18.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 6.22.1 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Version 6.22.2 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Version 6.24.1 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Version 6.26.0 just got published.
Your tests are still failing with this version. Compare the changes 🚨