-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of mocha is breaking the build 🚨 #4
Comments
After pinning to 6.0.2 your tests are passing again. Downgrade this dependency 📌. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.1.16.1.1 / 2019-04-07🐛 Fixes
|
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.1.26.1.2 / 2019-04-08🐛 Fixes
|
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 10 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.1.46.1.4 / 2019-04-18🔒 Security Fixes
CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.2.06.2.0 / 2019-07-18🎉 Enhancements
🐛 Fixes
📖 Documentation
🔍 Coverage
🔩 Other
CommitsThe new version differs by 52 commits.
There are 52 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 63 commits.
There are 63 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.2.26.2.2 / 2019-10-18🐛 Fixes
📖 Documentation
CommitsThe new version differs by 75 commits.
There are 75 commits in total. See the full diff |
The devDependency mocha was updated from
6.0.2
to6.1.0
.🚨 View failing branch.
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 for v6.1.0
6.1.0 / 2019-04-07
🔒 Security Fixes
🎉 Enhancements
options
parameter (@plroebuck).jsonc
extension (@sstephant)📠 Deprecations
These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:
this.skip()
for "after all" hooks (@juergba)🐛 Fixes
this.skip()
in "before each" hooks (@juergba)--allow-uncaught
for uncaught exceptions thrown inside hooks (@givanse)and some regressions:
Suite
cloning by copyingroot
property (@fatso83)📖 Documentation
🔩 Other
Commits
The new version differs by 28 commits.
f4fc95a
Release v6.1.0
bd29dbd
update CHANGELOG for v6.1.0 [ci skip]
aaf2b72
Use cwd-relative pathname to load config file (#3829)
b079d24
upgrade deps as per npm audit fix; closes #3854
e87c689
Deprecate this.skip() for "after all" hooks (#3719)
81cfa90
Copy Suite property "root" when cloning; closes #3847 (#3848)
8aa2fc4
Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
586bf78
Update JS-YAML to address security issue (#3845)
d1024a3
Update doc examples "tests.html" (#3811)
1d570e0
Delete "/docs/example/chai.js"
ade8b90
runner.js: "self.test" undefined in Browser (#3835)
0098147
Replace findup-sync with find-up for faster startup (#3830)
d5ba121
Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
a3089ad
update package-lock
75430ec
Upgrade yargs-parser dependency to avoid loading 2 copies of yargs
There are 28 commits in total.
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 🌴
The text was updated successfully, but these errors were encountered: