co-mocha@1.2.0 breaks build 🚨

[greenkeeperio-bot]

Hello lovely humans,

co-mocha just published its new version 1.2.0.

State	Failing tests 🚨
Dependency	co-mocha
New version	1.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As co-mocha 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 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

The new version differs by 5 commits .

• 629d988 v1.2.0
• ca58c53 chore(package): update browserify to version 14.0.0 (#30)
• 532a9e4 Use mocha constructor name find instance
• 9bc0f57 chore(package): update regenerator to version 0.9.0 (#26)
• ce833cf chore(package): update dependencies (#25)

See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage remained the same at 100.0% when pulling 6de8bff on greenkeeper-co-mocha-1.2.0 into 98888f9 on master.