You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
This version is covered by your current version range and after updating it in your project the build failed.
mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
❌ ci/circleci: node9 Your tests failed on CircleCI Details
✅ ci/circleci: node8 Your tests passed on CircleCI! Details
✅ ci/circleci: node6 Your tests passed on CircleCI! Details
✅ ci/circleci: node4 Your tests passed on CircleCI! Details
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);
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').
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 5.0.2 of mocha was just published.
This version is covered by your current version range and after updating it in your project the build failed.
mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
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!
🐛 Fixes
#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
Runnerinstance will emit theendevent 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-stdoutto v1.3.1 (@honzajavorek)Commits
The new version differs by 13 commits.
f2ee53cRelease v5.0.2ff1bd9eupdate package-lock.json6a796cbprepare CHANGELOG for v5.0.2 [ci skip]0542c40update README.md; closes #3191 [ci skip]afcd08fadd MAINTAINERS.md to .fossaignore [ci skip]3792befadd opencollective header image to assets/5078fc5persist paths in stack trace which have cwd as infix2c720a3do not eat exceptions thrown asynchronously from passed tests; closes #32263537061Update to correctly licensed browser-stdout versionec8901aremove unused functionality in utils modulef71f347rename wallaby.js -> .wallaby.jsc4ef568fix PR url73d55acfix typos in changelog [ci skip]See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴