An in-range update of coveralls is breaking the build 🚨
Closed this issue · 0 comments
greenkeeper commented
Version 2.13.1 of coveralls just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | coveralls |
| Current Version | 2.13.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As coveralls 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
- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/jescalan/spike-core/build/1.0.8),- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/static-dev/spike-core/builds/226575378),- ✅ **coverage/coveralls** First build on greenkeeper/coveralls-2.13.1 at 98.311% [Details](https://coveralls.io/builds/11278306)Commits
The new version differs by 1 commits0.
b9032a1better Jenkins detection
false
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 🌴