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

• ❌ ci/dockercloud: Your image failed to build in Docker Cloud (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (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

[greenkeeper]

• The devDependency mocha was updated from 6.0.2 to 6.1.0.

Your tests are still failing with this version. Compare changes

Release Notes for v6.1.0

6.1.0 / 2019-04-07

🔒 Security Fixes

• #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

🎉 Enhancements

• #3766: Make reporter constructor support optional options parameter (@plroebuck)
• #3760: Add support for config files with .jsonc extension (@sstephant)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

• #3719: Deprecate this.skip() for "after all" hooks (@juergba)

🐛 Fixes

• #3829: Use cwd-relative pathname to load config file (@plroebuck)
• #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
• #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

• #3848: Fix Suite cloning by copying root property (@fatso83)
• #3816: Guard against undefined timeout option (@boneskull)
• #3814: Update "yargs" in order to avoid deprecation message (@boneskull)
• #3788: Fix support for multiple node flags (@aginzberg)

📖 Documentation

• mochajs/mocha-examples: New repository of working examples of common configurations using mocha (@craigtaub)
• #3850: Remove pound icon showing on header hover on docs (@jd2rogers2)
• #3812: Add autoprefixer to documentation page CSS (@Munter)
• #3811: Update doc examples "tests.html" (@DavidLi119)
• #3807: Mocha website HTML tweaks (@plroebuck)
• #3793: Update config file example ".mocharc.yml" (@cspotcode)

🔩 Other

• #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
• #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)

Commits

The new version differs by 28 commits.

• f4fc95a Release v6.1.0
• bd29dbd update CHANGELOG for v6.1.0 [ci skip]
• aaf2b72 Use cwd-relative pathname to load config file (#3829)
• b079d24 upgrade deps as per npm audit fix; closes #3854
• e87c689 Deprecate this.skip() for "after all" hooks (#3719)
• 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
• 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
• 586bf78 Update JS-YAML to address security issue (#3845)
• d1024a3 Update doc examples "tests.html" (#3811)
• 1d570e0 Delete "/docs/example/chai.js"
• ade8b90 runner.js: "self.test" undefined in Browser (#3835)
• 0098147 Replace findup-sync with find-up for faster startup (#3830)
• d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
• a3089ad update package-lock
• 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

There are 28 commits in total.

See the full diff

[greenkeeper]

• The devDependency mocha was updated from 6.1.0 to 6.1.1.

Your tests are still failing with this version. Compare changes

Release Notes for v6.1.1

6.1.1 / 2019-04-07

🐛 Fixes

• Fix Windows End-of-Line publishing issue

Commits

The new version differs by 3 commits.

• 9b516bf Release v6.1.1
• 9e138b1 update CHANGELOG for v6.1.1 [ci skip]
• d7de948 Set eol for publishing

See the full diff

[greenkeeper]

• The devDependency mocha was updated from 6.1.1 to 6.1.2.

Your tests are still failing with this version. Compare changes

Release Notes for v6.1.2

6.1.2 / 2019-04-08

🐛 Fixes

• #3867: Re-publish v6.1.1 from POSIX OS to avoid dropped executable flags (@boneskull)

Commits

The new version differs by 2 commits.

• 86cd699 Release v6.1.2
• 2e8f31f update CHANGELOG for v6.1.2

See the full diff

[greenkeeper]

• The devDependency mocha was updated from 6.1.2 to 6.1.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

• f1fe632 Release v6.1.3
• ae3d53f update CHANGELOG for v6.1.3 [ci skip]
• e73941a upgrade node-environment-flags; closes #3868
• 5121211 Do not pass argv twice
• f05a58f Fix yargs global pollution

See the full diff

[greenkeeper]

• The devDependency mocha was updated from 6.1.3 to 6.1.4.

Your tests are still failing with this version. Compare changes

Release Notes for v6.1.4

6.1.4 / 2019-04-18

🔒 Security Fixes

• #3877: Upgrade js-yaml, addressing code injection vulnerability (@bjornstar)

Commits

The new version differs by 3 commits.

• 31c019e Release v6.1.4
• c3d241e update CHANGELOG.md for v6.1.4 [ci skip]
• 0d9d4a3 Update js-yaml from 3.13.0 to 3.13.1 (#3877)

See the full diff