The version 3.5.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of mocha.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.
WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!
2408d90Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th
68a1466Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue
958fbb4Update new tests to work in browser per test hierarchy reorganization
1df7c94Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js
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).
Version 3.5.0 of mocha just got published.
The version 3.5.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of mocha. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
free-as-in-freezing3.5.0 / 2017-07-31
--forbid-onlyand--forbid-pendingflags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)--napi-modulesflag (@jupp0r)Commits
The new version differs by 34 commits.
82d879fRelease v3.5.0bf687ceupdate mocha.js for v3.5.0ec73c9aupdate date for release of v3.5.0 in CHANGELOG [ci skip]1ba2cfcupdate CHANGELOG.md for v3.5.0 [ci skip]065e14eremove custom install script from travis (no longer needed)4e87046update karma-sauce-launcher URL for npm@56886cccincrease timeout for slow-grepping test2408d90Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th68a1466Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue958fbb4Update new tests to work in browser per test hierarchy reorganization1df7c94Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js1f270cdStop timing out (#2889)27c7496upgrade to debug@2.6.8; closes #2859 (#2860)50fc47dfix CI; closes #2867 (#2868)1b1377cAdd test for ignoreLeaks and fix descriptionsThere are 34 commits in total.
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: