LeadingEdgeForum/atlas2

An in-range update of mocha is breaking the build 🚨

Closed this issue Β· 1 comments

Version 5.0.0 of mocha was just published.

Branch Build failing 🚨
Dependency mocha
Current Version 4.1.0
Type devDependency

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
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v5.0.0

5.0.0 / 2018-01-17

Mocha starts off 2018 right by again dropping support for unmaintained rubbish.

Welcome @vkarpov15 to the team!

πŸ’₯ Breaking Changes

  • #3148: Drop support for IE9 and IE10 (@Bamieh)
    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.

πŸŽ‰ Enhancements

πŸ› Fixes

😎 Developer Experience

πŸ“– Documentation

πŸ”© Other

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. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

After pinning to 4.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.