greenkeeper[bot]
commented
7 years ago Version 3.4.1 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Release Notes
Ohai CRLF...Fixed a publishing mishap with git's autocrlf settings.
Version 3.4.0 of mocha just got published.
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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/nteract/jupyter-paths/builds/232160166?utm_source=github_status&utm_medium=notification),- ✅ **continuous-integration/appveyor/branch** AppVeyor build succeeded [Details](https://ci.appveyor.com/project/nteract/jupyter-paths/build/1.0.25)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)--no-warningsand--trace-warningsflags (@sonicdoe)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 statusfalse
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: