Skip to content
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

Update mocha to 5.2.0-close #9

Closed
wants to merge 1 commit into from
Closed

Update mocha to 5.2.0-close #9

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 20, 2018

This PR contains the following updates:

Package Type Update Change References
mocha devDependencies major 3.5.3 -> 5.2.0 homepage, source

Release Notes

mochajs/mocha

v5.2.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔩 Other

v5.1.1

Compare Source

🐛 Fixes

  • #​3325: Revert change which broke --watch ([@​boneskull])

v5.1.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔩 Other

v5.0.5

Compare Source

Welcome @​outsideris to the team!

🐛 Fixes

📖 Documentation

🔩 Other

v5.0.4

Compare Source

🐛 Fixes

v5.0.3

Compare Source

This patch features a fix to address a potential "low severity" ReDoS vulnerability in the diff package (a dependency of Mocha).

🔒 Security Fixes

🔩 Other

v5.0.2

Compare Source

This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!

🐛 Fixes

  • #​3226: Do not swallow errors that are thrown asynchronously from passing tests ([@​boneskull]). Example:

    it('should actually fail, sorry!', function (done) {
      // passing assertion
      assert(true === true);
    
      // test complete & is marked as passing
      done();
    
      // ...but something evil lurks within
      setTimeout(() => {
        throw new Error('chaos!');
      }, 100);
    });

    Previously to this version, Mocha would have silently swallowed the chaos! exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.

    Maintainers of external reporters: If a test of this class is encountered, the Runner instance will emit the end event twice; you may need to change your reporter to use runner.once('end') intead of runner.on('end').

  • #​3093: Fix stack trace reformatting problem (@​outsideris)

🔩 Other

v5.0.1

Compare Source

...your garden-variety patch release.

Special thanks to Wallaby.js for their continued support! ❤️

🐛 Fixes

📖 Documentation

🔩 Other

v5.0.0

Compare Source

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

v4.1.0

Compare Source

This is mainly a "housekeeping" release.

Welcome @​Bamieh and @​xxczaki to the team!

🐛 Fixes

🎉 Enhancements

  • #​2514: The --no-diff flag will completely disable diff output (@​CapacitorSet)
  • #​3058: All "setters" in Mocha's API are now also "getters" if called without arguments ([@​makepanic])

📖 Documentation

🔩 Other

v4.0.1

Compare Source

🐛 Fixes

v4.0.0

Compare Source

You might want to read this before filing a new bug! 😝

💥 Breaking Changes

For more info, please read this article.

Compatibility
  • #​3016: Drop support for unmaintained versions of Node.js ([@​boneskull]):
    • 0.10.x
    • 0.11.x
    • 0.12.x
    • iojs (any)
    • 5.x.x
  • #​2979: Drop support for non-ES5-compliant browsers ([@​boneskull]):
    • IE7
    • IE8
    • PhantomJS 1.x
  • #​2615: Drop Bower support; old versions (3.x, etc.) will remain available ([@​ScottFreeCode], [@​boneskull])
Default Behavior
  • #​2879: By default, Mocha will no longer force the process to exit once all tests complete. This means any test code (or code under test) which would normally prevent node from exiting will do so when run in Mocha. Supply the --exit flag to revert to pre-v4.0.0 behavior ([@​ScottFreeCode], [@​boneskull])
Reporter Output
  • #​2095: Remove stdout: prefix from browser reporter logs (@​skeggse)
  • #​2295: Add separator in "unified diff" output (@​olsonpm)
  • #​2686: Print failure message when --forbid-pending or --forbid-only is specified ([@​ScottFreeCode])
  • #​2814: Indent contexts for better readability when reporting failures ([@​charlierudolph])

👎 Deprecations

  • #​2493: The --compilers command-line option is now soft-deprecated and will emit a warning on STDERR. Read this for more info and workarounds ([@​ScottFreeCode], [@​boneskull])

🎉 Enhancements

📖 Documentation

🔩 Other

  • #​2890: Speed up build by (re-)consolidating SauceLabs tests ([@​boneskull])

Renovate configuration

📅 Schedule: No schedule defined.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.


This PR has been generated by Renovate Bot. View repository job log here.

@coveralls
Copy link

coveralls commented Mar 20, 2018

Coverage Status

Coverage remained the same at 74.576% when pulling e483353 on renovate/mocha-5.x into bb0edf5 on dev.

@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 0d22750 to 2a08206 Compare March 23, 2018 01:43
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 2a08206 to 432d0ac Compare April 1, 2018 21:01
@renovate renovate bot force-pushed the renovate/mocha-5.x branch 2 times, most recently from 7fe9c45 to 3d7d8d5 Compare April 16, 2018 05:18
@renovate renovate bot changed the title Update dependency mocha to v5 Update mocha to 5.1.0 Apr 17, 2018
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 3d7d8d5 to f361d46 Compare April 18, 2018 17:39
@renovate renovate bot changed the title Update mocha to 5.1.0 Update mocha to 5.1.1 Apr 18, 2018
@renovate renovate bot force-pushed the renovate/mocha-5.x branch 2 times, most recently from 3c17e74 to 7aa308c Compare April 30, 2018 03:16
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 7aa308c to 5326daa Compare May 18, 2018 23:40
@renovate renovate bot changed the title Update mocha to 5.1.1 Update mocha to 5.2.0 May 18, 2018
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 5326daa to 388de84 Compare May 23, 2018 23:15
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 388de84 to e483353 Compare July 27, 2018 08:13
@sbardian sbardian changed the title Update mocha to 5.2.0 Update mocha to 5.2.0-close Oct 2, 2018
@sbardian sbardian closed this Oct 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants