Closed greenkeeper[bot] closed 6 years ago
Merging #47 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #47 +/- ##
=======================================
Coverage 94.73% 94.73%
=======================================
Files 5 5
Lines 190 190
=======================================
Hits 180 180
Misses 10 10
Continue to review full report at Codecov.
Legend - Click here to learn more
ฮ = absolute <relative> (impact)
,รธ = not affected
,? = missing data
Powered by Codecov. Last update 284e180...9c4eee6. Read the comment docs.
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
Version 5.0.0 of mocha was just published.
The version 5.0.0 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.05.0.0 / 2018-01-17
Mocha starts off 2018 right by again dropping support for unmaintained rubbish.
Welcome @vkarpov15 to the team!
Practically speaking, only code which consumes (through bundling or otherwise) the userland buffer module should be affected. However, Mocha will no longer test against these browsers, nor apply fixes for them.
--file
command line argument (documentation) (@hswolff)--no-timeouts
docs (@dfberry)done()
callback docs (@maraisr)README.md
organization (@xxczaki)Commits
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
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: