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

[greenkeeper]

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/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/jcoreio/redux-utils/builds/226574517),- ✅ **coverage/coveralls** First build on greenkeeper/coveralls-2.13.1 at 100.0% [Details](https://coveralls.io/builds/11278102)

---

Commits

The new version differs by 1 commits0.

• b9032a1 better 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 🌴

[greenkeeper]

Version 2.13.2 just got published.

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

Commits

The new version differs by 3 commits.

• 5ebe57f bump version
• 428780c Expand allowed dependency versions to all API compatible versions (#172)
• eb1b723 Update Mocha link (#169)

See the full diff

[greenkeeper]

Version 2.13.3 just got published.

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

Commits

The new version differs by 2 commits.

• b2a86d6 legacy 2.x version branch for node <= 4.x
• eb1b723 Update Mocha link (#169)

See the full diff