coveralls
commented
7 years ago Coverage remained the same at 100.0% when pulling 6ad43cfbf410eadb6ac93f20aeb41efacac971a3 on greenkeeper-mocha-3.4.0 into 1650ef65626170a7035d503b5df93c57d8a53375 on master.
Hello lovely humans,
mocha just published its new version 3.4.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As 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 :muscle:
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 :sparkles:
You rock!
:palm_tree:
GitHub Release
Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.
This week's highlights:
allowUncaughtadded to commandline as--allow-uncaught(and bugfixed)--no-warningsand--trace-warningsflags (@sonicdoe)