Closed greenkeeper[bot] closed 6 years ago
Update to this version instead 🚀
This patch features a fix to address a potential "low severity" ReDoS vulnerability in the diff package (a dependency of Mocha).
generateDiff()
in Base
reporter (@harrysarson)The new version differs by 6 commits.
da6e5c9
Release v5.0.3
70d9262
update CHANGELOG.md for v5.0.3 [ci skip]
aaaa5ab
fix: ReDoS vuln in mocha@5.0.2 › diff@3.3.1 (#3266)
8df5727
Tidies up code after review
660bccc
adds unit tests covering Base.generateDiff
bdcb3c3
exposes generateDiff function from base reporter
See the full diff
Update to this version instead 🚀
Update to this version instead 🚀
Welcome @outsideris to the team!
--bail
failing to bail within hooks (@outsideris)describe.skip()
) (@outsideris)CHANGELOG.md
(@tagoro9, @honzajavorek)The new version differs by 18 commits.
c11e1e2
Release v5.0.5
b5a556e
add changes for v5.0.5 [ci skip]
424ef84
increase default timeout for browser unit tests
19104e3
fix debug msg in Runnable#slow; closes #2952
f4275b6
extract checking AMD bundle as own test
19b764d
Addressed feedback
2c19503
Fixed linting
ab84f02
chore(docs): rewording pending tests
6383916
fix to bail option works properly with hooks (#3278)
0060884
keep hierarchy for skipped suites w/o a callback
39df783
docs: Fix typo in an emoji
27af2cf
fix(changelog): update links to some PRs
d76f490
chore(ci): Remove PHANTOMJS_CDNURL, nit
86af6bb
fix my carelessness in e19e879
e19e879
ensure lib/mocha.js is not ignored by ESLint
There are 18 commits in total.
See the full diff
☝️ 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 54 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]
09ce746
Release v5.0.1
70027b6
update changelog for v5.0.1 [ci skip]
There are 54 commits in total.
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: