Open greenkeeper[bot] opened 7 years ago
Update to this version instead 🚀
The new version differs by 6 commits.
eb8bf8d
Release v4.0.1
3b485ea
update CHANGELOG.md for v4.0.1 [ci skip]
96e5c1a
upgrade eslint to v4.8.0
d7cff37
Update growl to 1.10.3
0cdd921
remove preversion script; test on publish; closes #2999
f49c0ce
Fix changelog issues/pr URLs (#3047)
See the full diff
Update to this version instead 🚀
This is mainly a "housekeeping" release.
Welcome @Bamieh and @xxczaki to the team!
progress
reporter now accepts reporter options (@canoztokmak)xit
in bdd
interface now properly returns its Test
object (@Bamieh)--help
will now help you even if you have a mocha.opts
(@Zarel)--no-diff
flag will completely disable diff output (@CapacitorSet)docs/
(@boneskull)The new version differs by 409 commits.
6b9ddc6
Release v4.1.0
3c4b116
update CHANGELOG for v4.1.0
5be22b2
options.reporterOptions
are used for progress reporter
ea96b18
add .fossaignore [ci skip]
adc67fd
Revert "[ImgBot] optimizes images (#3175)"
ae3712c
[ImgBot] optimizes images (#3175)
33db6b1
Use x64 node on appveyor
4a6e095
Run appveyor tests on x64 platform. Might enable sharp installation
3abed9b
Lint netlify-headers script
119543e
Add preconnect for doubleclick domain that google analytics results in contacting
bd5109e
Remove crossorigin='anonymous' from preconnect hints. Only needed for fonts, xhr and es module loads
123ee4f
Handle the case where all avatars are already loaded at the time when the script exexecutes
64deadc
Specific value for inlining htmlimages to guarantee logo is inlined
8f1ded4
https urls where possible
d5a5125
Be explicit about styling of screenshot images
There are 250 commits in total.
See the full diff
Update to this version instead 🚀
Mocha starts off 2018 right by again dropping support for unmaintained rubbish.
Welcome @vkarpov15 to the team!
--file
command line argument (documentation) (@hswolff)--no-timeouts
docs (@dfberry)done()
callback docs (@maraisr)README.md
organization (@xxczaki)The new version differs by 26 commits.
cc4a818
Release v5.0.0
9f61c04
finalize v5.0.0 CHANGELOG [ci skip]
a7267b4
remove more references to make and Makefile
dc58252
prep changelog for v5.0.0 [ci skip]
f8a1d2a
docs(index): add missing doc link (#3203); closes #3135
401997f
update package-lock.json
50aec7a
Add ability to pass in test files to be ran before positional files via --file (#3190)
7d8abe0
fix id and class definition
0a3e32b
Rewrite Makefile using NPS Scripts. Closes #2352
c7730a6
Drop TextMate integration inside mocha closes #3118
5c6e99b
update ESM tests to run against headless chrome instead of saucelabs' chrome only
ac1dd70
attempt to get travis working again
e8b5592
Align netlify config with admin panel
565726d
Added Netlify config file
e54370e
replace phantomjs with puppeteer for browser tests; closes #3128
There are 26 commits in total.
See the full diff
Update to this version instead 🚀
The new version differs by 15 commits.
09ce746
Release v5.0.1
70027b6
update changelog for v5.0.1 [ci skip]
44aae9f
add working wallaby config
412cf27
[Update] license year
b7377b3
rename help-wanted to "help wanted" in stale.yml
d975a6a
fix memory leak when run in v8; closes #3119
3509029
update .gitignore to only ignore root mocha.js [ci skip]
b57f623
fix: When using --delay, .only() no longer works. Issue #1838
cd74322
Slight copy update on docs for test directory
f687d2b
update docs for the glob
14fc030
Add all supported wallaby editors
2e7e4c0
rename "common-mistake" label to "faq"
bca57f4
clarify docs on html, xunit and 3p reporters; closes #1906
2fe2d01
Revert "fix travis "before script" script"
c0ac1b9
fix travis "before script" script
See the full diff
Update to this version instead 🚀
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:
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 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')
.
#3093: Fix stack trace reformatting problem (@outsideris)
browser-stdout
to v1.3.1 (@honzajavorek)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
Version 4.0.0 of mocha just got published.
The version 4.0.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
v4.0.04.0.0 / 2017-10-02
You might want to read this before filing a new bug!😝
For more info, please read this article.
Compatibility
Default Behavior
node
from exiting will do so when run in Mocha. Supply the--exit
flag to revert to pre-v4.0.0 behavior (@ScottFreeCode, @boneskull)Reporter Output
stdout:
prefix from browser reporter logs (@skeggse)--forbid-pending
or--forbid-only
is specified (@ScottFreeCode)--compilers
command-line option is now soft-deprecated and will emit a warning onSTDERR
. Read this for more info and workarounds (@ScottFreeCode, @boneskull)README.md
andCONTRIBUTING.md
(@skeggse)Commits
The new version differs by 48 commits.
d69bf14
Release v4.0.0
171b9f9
pfix "prepublishOnly" potential portability problem
60e39d9
Update link to wiki (GitHub at the leading
--
)804f9d5
Update link because GitHub ate the leading
--
3326c23
update CHANGELOG for v4.0.0 [ci skip]
6dd9252
add link to wiki on --compilers deprecation
96318e1
Deprecate --compilers
92beda9
drop bower support
58a4c6a
remove unused .npmignore
7af6611
kill Date#toISOString shim
43501a2
reduce noise about slow tests; make a few tests faster, etc.
fa228e9
update --exit / --no-exit integration test for new default behavior
3fdd3ff
Switch default from forced exit to no-exit
c5d69e0
add integration tests for --exit/--no-exit
3a7f8dc
enhance runMochaJSON() helper by returning the subprocess instance
There are 48 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: