Closed greenkeeper[bot] closed 7 years ago
Merging #42 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #42 +/- ##
=======================================
Coverage 95.76% 95.76%
=======================================
Files 46 46
Lines 1323 1323
Branches 191 191
=======================================
Hits 1267 1267
Misses 22 22
Partials 34 34
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update d4331a6...26d76a2. Read the comment docs.
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-only
and--forbid-pending
flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)--napi-modules
flag (@jupp0r)Commits
The new version differs by 34 commits.
82d879f
Release v3.5.0
bf687ce
update mocha.js for v3.5.0
ec73c9a
update date for release of v3.5.0 in CHANGELOG [ci skip]
1ba2cfc
update CHANGELOG.md for v3.5.0 [ci skip]
065e14e
remove custom install script from travis (no longer needed)
4e87046
update karma-sauce-launcher URL for npm@5
6886ccc
increase timeout for slow-grepping test
2408d90
Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th
68a1466
Try 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
958fbb4
Update new tests to work in browser per test hierarchy reorganization
1df7c94
Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js
1f270cd
Stop timing out (#2889)
27c7496
upgrade to debug@2.6.8; closes #2859 (#2860)
50fc47d
fix CI; closes #2867 (#2868)
1b1377c
Add test for ignoreLeaks and fix descriptions
There 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: