The version 3.2.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.
Under the foundation, all contributors to Mocha must sign the JS Foundation CLA before their code can be merged. When sending a PR--if you have not already signed the CLA--a friendly bot will ask you to do so.
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 95.413% when pulling eacfc43edc824f3d5dba55dcab9f9f31568ae263 on greenkeeper/mocha-3.2.0 into 3cf4cf781fe0e3fe362b408ed43590007803c340 on master.
Version 3.2.0 of mocha just got published.
The version 3.2.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
testing-coma3.2.0 / 2016-11-24
Mocha is now a JS Foundation Project!
Mocha is proud to have joined the JS Foundation. For more information, read the announcement.
Contributor License Agreement
Under the foundation, all contributors to Mocha must sign the JS Foundation CLA before their code can be merged. When sending a PR--if you have not already signed the CLA--a friendly bot will ask you to do so.
Mocha remains licensed under the MIT license.
--watch
encounters broken symlinks (@villesau)list
reporter (@Aldaviva)--inspect
flag to CLI help (@ughitsaaron)README.md
(@boneskull, @ScottFreeCode, @dasilvacontin)Thanks to all our contributors, sponsors and backers! Keep on the lookout for a public roadmap and new contribution guide coming soon.
Commits
The new version differs by 21 commits .
b51e360
Release v3.2.0
5badf0b
rebuild mocha.js for release v3.2.0 [ci skip]
b1d6b49
update
CHANGELOG.md
for v3.2.0 [ci skip]7a05a6c
use spec reporter in tests by default; closes #2594
004389f
tweak timeout messaging; see #2294
12afaf7
cleanup .gitignore [ci skip]
edde033
fix XUnit reporter output. Closes #2584
f5bef7c
Revert test pass symbol in List reporter
4a2e85a
ignore files files which are not found by files() (#2538)
79d7414
Add Browser Support Matrix to README.md (#2590) [ci skip]
1d52fd3
use karma-mocha; closes #2570
8941442
adds info about --inspect flag to options in --help
71e7a1e
rename some fixture files that had the wrong extension
1a45929
typo in comment
b5a424a
Link license from current branch
There are 21 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: