An in-range update of mocha is breaking the build 🚨
Closed this issue · 1 comments
Version 3.4.0 of mocha just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | mocha |
| Current Version | 3.3.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ bitHound - Code 3 failing files. Details,- ✅ bitHound - Dependencies No failing dependencies. Details,- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details,- ✅ security/snyk No new vulnerabilities Details,- ✅ continuous-integration/travis-ci/pr The Travis CI build passed Details,- ✅ coverage/coveralls Coverage remained the same at 93.651% Details,- ✅ codecov/patch Coverage not affected when comparing d975fad...4c01236 Details,- ✅ codecov/project 93.65% remains the same compared to d975fad Details
Release Notes
v3.4.0Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.
This week's highlights:
allowUncaughtadded to commandline as--allow-uncaught(and bugfixed)- warning-related Node flags
🎉 Enhancements
- #2793, #2697: add --allowUncaught to Node.js (@lrowe)
- #2733: Add
--no-warningsand--trace-warningsflags (@sonicdoe)
🐛 Fixes
🔩 Other
- #2778: Add license report and scan status (@xizhao)
- #2794: no special case for macOS running Karma locally (@boneskull)
- #2795: reverts use of semistandard directly ([#2648]) (@boneskull)
Commits
The new version differs by 9 commits0.
7554b31Add Changelog for v3.4.09f7f7edAdd--trace-warningsflag92561c8Add--no-warningsflagceee976lint test/integration/fixtures/simple-reporter.jsdcfc094Revert "usesemistandarddirectly"93392ddno special case for macOS running Karma locally4d1d91d--allow-uncaught cli optionfb1e083fix allowUncaught in browser4ed3fc5Add license report and scan status
false
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Version 3.4.1 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Release Notes
Ohai CRLF...Fixed a publishing mishap with git's autocrlf settings.