An in-range update of mocha is breaking the build 🚨
greenkeeper opened this issue · comments
Version 3.4.1 of mocha just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | mocha |
| Current Version | 3.4.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
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
Ohai CRLF...Fixed a publishing mishap with git's autocrlf settings.
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.2 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Release Notes
fake-success3.4.2 / 2017-05-24
🐛 Fixes
- #2802: Remove call to deprecated os.tmpDir (@makepanic)
- #2820: Eagerly set process.exitCode (@chrisleck)
🔩 Other
Commits
The new version differs by 7 commits.
a15b20a:ship: Release v3.4.2fc802a9:memo: Add Changelog for v3.4.210ff0ecEagerly set process.exitCode (#2820)fc35691Merge pull request #2818 from makepanic/issue/28023e7152fRemove call to deprecated os.tmpDir (#2802)e249434Merge pull request #2807 from mochajs/npm-script-lint17a1770Move linting into an npm script. Relates to #2805
See the full diff