chore(deps): update dependency mocha to v5.2.0 - abandoned #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.0.1->5.2.0Release Notes
mochajs/mocha
v5.2.0Compare Source
🎉 Enhancements
mocha.opts(@plroebuck)🐛 Fixes
beforehooks when using--bail(@outsideris)📖 Documentation
🔩 Other
Buffer.from()(@harrysarson)v5.1.1Compare Source
🐛 Fixes
--watch(@boneskull)v5.1.0Compare Source
🎉 Enhancements
--excludeoption (@metalex9)🐛 Fixes
📖 Documentation
🔩 Other
v5.0.5Compare Source
Welcome @outsideris to the team!
🐛 Fixes
--bailfailing to bail within hooks (@outsideris)describe.skip()) (@outsideris)📖 Documentation
CHANGELOG.md(@tagoro9, @honzajavorek)🔩 Other
v5.0.4Compare Source
🐛 Fixes
v5.0.3Compare Source
This patch features a fix to address a potential "low severity" ReDoS vulnerability in the diff package (a dependency of Mocha).
🔒 Security Fixes
diffto v3.5.0 (@anishkny)🔩 Other
generateDiff()inBasereporter (@harrysarson)v5.0.2Compare Source
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:
```js
it('should actually fail, sorry!', function (done) {
// passing assertion
assert(true === true);
// test complete & is marked as passing
done();
// ...but something evil lurks within
setTimeout(() => {
throw new Error('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
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)
🔩 Other
browser-stdoutto v1.3.1 (@honzajavorek)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.