The version 5.0.2 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of mocha.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv5.0.2
5.0.2 / 2018-03-05
This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!
š Fixes
#3226: Do not swallow errors that are thrown asynchronously from passing tests (@boneskull). Example:
it('should actually fail, sorry!', function (done) {
// passing assertionassert(true===true);
// test complete & is marked as passingdone();
// ...but something evil lurks withinsetTimeout(() => {
thrownewError('chaos!');
}, 100);
});
Previously to this version, Mocha would have silently swallowed the chaos! exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.
Maintainers of external reporters: If a test of this class is encountered, the Runner instance will emit the end event twice; you may need to change your reporter to use runner.once('end') intead of runner.on('end').
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 5.0.2 of mocha was just published.
The version 5.0.2 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of mocha.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v5.0.25.0.2 / 2018-03-05
This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!
#3226: Do not swallow errors that are thrown asynchronously from passing tests (@boneskull). Example:
Previously to this version, Mocha would have silently swallowed the
chaos!
exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.Maintainers of external reporters: If a test of this class is encountered, the
Runner
instance will emit theend
event twice; you may need to change your reporter to userunner.once('end')
intead ofrunner.on('end')
.#3093: Fix stack trace reformatting problem (@outsideris)
:nut_and_bolt Other
browser-stdout
to v1.3.1 (@honzajavorek)Commits
The new version differs by 13 commits.
f2ee53c
Release v5.0.2
ff1bd9e
update package-lock.json
6a796cb
prepare CHANGELOG for v5.0.2 [ci skip]
0542c40
update README.md; closes #3191 [ci skip]
afcd08f
add MAINTAINERS.md to .fossaignore [ci skip]
3792bef
add opencollective header image to assets/
5078fc5
persist paths in stack trace which have cwd as infix
2c720a3
do not eat exceptions thrown asynchronously from passed tests; closes #3226
3537061
Update to correctly licensed browser-stdout version
ec8901a
remove unused functionality in utils module
f71f347
rename wallaby.js -> .wallaby.js
c4ef568
fix PR url
73d55ac
fix typos in changelog [ci skip]
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: