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

[greenkeeper]

The devDependency mocha was updated from 6.0.0 to 6.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v6.0.1

6.0.1 / 2019-02-21

The obligatory round of post-major-release bugfixes.

🐛 Fixes

These issues were regressions.

• #3754 - Mocha again finds test.js when run without arguments (@plroebuck)
• #3756 - Mocha again supports third-party interfaces via --ui (@boneskull)
• #3755 - Fix broken --watch (@boneskull)
• #3759 - Fix unwelcome deprecation notice when Mocha run against languages (CoffeeScript) with implicit return statements; returning a non-undefined value from a describe callback is no longer considered deprecated (@boneskull)

📖 Documentation

• #3738 - Upgrade to @mocha/docdash@2 (@tendonstrength)
• #3751 - Use preferred names for example config files (@Szauka)

Commits

The new version differs by 9 commits.

• 6d3d6b4 Release v6.0.1
• 2146ece update CHANGELOG.md for v6.0.1
• 7c9221d backout deprecation of value returned from suite; closes #3744
• b7cfceb fix --watch not finding any files to execute; closes #3748
• b836d73 Upgrade docdash version - issue #3663
• 7926f47 fix --ui issues, closes #3746
• 00f2ed9 dev dep upgrades from "npm audit" and "npm upgrade"
• 34afb1a fix(cli/run.js): Revert default glob to match Mocha-5.2
• 6d5a0db Bring the example congfiguration file in line with the documentation. (#3751)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 6.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency mocha was updated from 6.0.1 to 6.0.2.

Your tests are still failing with this version. Compare changes

Release Notes for v6.0.2

6.0.2 / 2019-02-25

🐛 Fixes

Two more regressions fixed:

• #3768: Test file paths no longer dropped from mocha.opts (@boneskull)
• #3767: --require does not break on module names that look like certain node flags (@boneskull)

Commits

The new version differs by 6 commits.

• 00a895f Release v6.0.2
• 1edce76 update CHANGELOG for v6.0.2 [ci skip]
• 347e9db fix broken positional arguments in config; ensure positional args are unique; closes #3763
• 9e31e9d fix handling of bareword args matching node flags; closes #3761
• 6535965 Update "karma-browserify" to eliminate Karma middleware warning (#3762)
• 37febb6 improve issue template. (#3411)

See the full diff