An in-range update of coveralls is breaking the build 🚨

[greenkeeper]

Version 2.12.0 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.11.16
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/travis-ci/push The Travis CI build failed Details

• ✅ coverage/coveralls First build on greenkeeper/coveralls-2.12.0 at 95.652% Details

Release Notes

Branch coverage support

Adds branch coverage data to Coveralls API post.

Commits

The new version differs by 2 commits .

• d571dac merge, version bump
• 1575050 branching WIP

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 🌴

[greenkeeper]

Version 2.13.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 4 commits .

• 2821200 version bump
• ef7e811 Parse commit from packed refs if not available in refs dir. (#163)
• e476964 Merge pull request #162 from evanjbowling/patch-1
• 63a7f92 Update README.md

See the full diff.

[greenkeeper]

Version 2.13.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 5 commits0.

• b9032a1 better Jenkins detection
• 2821200 version bump
• ef7e811 Parse commit from packed refs if not available in refs dir. (#163)
• e476964 Merge pull request #162 from evanjbowling/patch-1
• 63a7f92 Update README.md

false

See the full diff