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

[greenkeeper[bot]]

Version 2.13.3 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.13.2
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 :muscle:

Status Details

- ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/13482837) - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/seangenabe/etagger/builds/281001453?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 1 commits ahead by 1, behind by 2.

• b2a86d6 legacy 2.x version branch for node <= 4.x

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 2.13.2 your tests are passing again. Downgrade this dependency 📌.

[seangenabe]

Obsolete: Updated to v3.0.0