The version 3.3.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 Notescoverave
Thanks to all our contributors, maintainers, sponsors, and users! ❤️
As highlights:
We've got coverage now!
Testing is looking less flaky \o/.
No more nitpicking about "mocha.js" build on PRs.
🎉 Enhancements
#2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
#2769: Support --inspect-brk on command-line (@igwejk)
🐛 Fixes
#2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)
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).
Coverage remained the same at 96.0% when pulling 41c9b8613e26cab7c8b0ed23e3651abc985cac11 on greenkeeper/mocha-3.3.0 into 1d3b0efe053b24d33e805cccb71647ec3243f872 on master.
Coverage remained the same at 96.0% when pulling 41c9b8613e26cab7c8b0ed23e3651abc985cac11 on greenkeeper/mocha-3.3.0 into 1d3b0efe053b24d33e805cccb71647ec3243f872 on master.
Coverage remained the same at 96.0% when pulling 41c9b8613e26cab7c8b0ed23e3651abc985cac11 on greenkeeper/mocha-3.3.0 into 1d3b0efe053b24d33e805cccb71647ec3243f872 on master.
Version 3.3.0 of mocha just got published.
The version 3.3.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
coveraveThanks to all our contributors, maintainers, sponsors, and users!❤️
As highlights:
--inspect-brk
on command-line (@igwejk)semistandard
directly (@kt3k)Commits
The new version differs by 89 commits0.
fb1687e
:ship: Release v3.3.0
1943e02
Add Changelog for v3.3.0
861e968
Refactor literal play-icon hex code to a var
1d3c5bc
Fix typo in karma.conf.js
9bd9389
Fix spec paths in test HTML files
0a93024
Adds tests for loading reporters w/ relative/absolute paths (#2773)
73929ad
Comment special treatment of '+' in URL query parsing
e2c9514
Merge pull request #2769 from igwejk/support_inspect_break_in_opts
038c636
Support
--inspect-brk
on command-lineb4ebabd
Merge pull request #2727 from lamby/reproducible-build
882347b
Please make the build reproducible.
a2fc76c
Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
ed61cd0
cover .some() function in utils.js with tests
f42cbf4
Merge pull request #2701 from craigtaub/landingSpec
6065242
use stubbed symbol
There are 89 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: