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

chore(deps): update dependency mocha to v5 #18

Merged
merged 1 commit into from
Jun 27, 2018
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 18, 2018

This Pull Request updates dependency mocha from v3.5.3 to v5.2.0

Release Notes

v5.2.0

Compare Source

🎉 Enhancements

  • #​3375: Add support for comments in mocha.opts (@​plroebuck)

🐛 Fixes

  • #​3346: Exit correctly from before hooks when using --bail (@​outsideris)

📖 Documentation

🔩 Other


v5.1.1

Compare Source

🐛 Fixes

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

v5.1.0

Compare Source

🎉 Enhancements

🐛 Fixes

  • #​3318: Fix failures in circular objects in JSON reporter (@​jeversmann, [@​boneskull])

📖 Documentation

🔩 Other

  • #​3302, #​3308, #​3310, #​3315, #​3316: Build matrix improvements (more info) (@​outsideris, [@​boneskull])
  • #​3272: Refactor reporter tests (@​jMuzsik)

v5.0.5

Compare Source
Welcome @​outsideris to the team!

🐛 Fixes

  • #​3096: Fix --bail failing to bail within hooks (@​outsideris)
  • #​3184: Don't skip too many suites (using describe.skip()) (@​outsideris)

📖 Documentation

🔩 Other

  • #​3208: Improve test coverage for AMD users (@​outsideris)
  • #​3267: Remove vestiges of PhantomJS from CI (@​anishkny)
  • #​2952: Fix a debug message ([@​boneskull])

v5.0.4

Compare Source

🐛 Fixes

  • #​3265: Fixes regression in "watch" functionality introduced in v5.0.2 (@​outsideris)

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

  • #​1838: --delay now works with .only() (@​silviom)
  • #​3119: Plug memory leak present in v8 ([@​boneskull])

📖 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

  • #​3187: Fix inaccurate test duration reporting (@​FND)
  • #​3202: Fix bad markup in HTML reporter (@​DanielRuf)

😎 Developer Experience

  • #​2352: Ditch GNU Make for nps to manage scripts (@​TedYav)

📖 Documentation

🔩 Other

  • #​3118: Move TextMate Integration to its own repo (@​Bamieh)
  • #​3185: Add Node.js v9 to build matrix; remove v7 (@​xxczaki)
  • #​3172: Markdown linting ([@​boneskull])
  • Test & Netlify updates (@​Munter, [@​boneskull])

v4.1.0

Compare Source
This is mainly a "housekeeping" release.

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

🐛 Fixes

  • #​2661: progress reporter now accepts reporter options (@​canoztokmak)
  • #​3142: xit in bdd interface now properly returns its Test object (@​Bamieh)
  • #​3075: Diffs now computed eagerly to avoid misinformation when reported (@​abrady0)
  • #​2745: --help will now help you even if you have a mocha.opts (@​Zarel)

🎉 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

  • #​3051: Upgrade Growl to v1.10.3 to fix its peer dep problems (@​dpogue)

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

  • #​2628: Allow override of default test suite name in XUnit reporter (@​ngeor)

📖 Documentation

  • #​3020: Link to CLA in README.md and CONTRIBUTING.md (@​skeggse)

🔩 Other

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


This PR has been generated by Renovate Bot.

@renovate renovate bot force-pushed the renovate/mocha-5.x branch 3 times, most recently from 82672e6 to 658d2cd Compare February 20, 2018 23:00
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 658d2cd to a79a01a Compare February 21, 2018 00:45
@renovate renovate bot force-pushed the renovate/mocha-5.x branch 3 times, most recently from 42eda1f to c3624ae Compare March 7, 2018 17:43
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from c3624ae to 9d9477c Compare March 23, 2018 01:53
@renovate renovate bot force-pushed the renovate/mocha-5.x branch 2 times, most recently from 613d03f to 9795068 Compare April 18, 2018 18:01
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5 Update dependency mocha to v5 May 9, 2018
@renovate renovate bot changed the title Update dependency mocha to v5 chore(deps): update dependency mocha to v5 May 9, 2018
@renovate renovate bot force-pushed the renovate/mocha-5.x branch from 9795068 to a92b59e Compare May 18, 2018 23:56
@renovate renovate bot merged commit 98e10e7 into master Jun 27, 2018
@renovate renovate bot deleted the renovate/mocha-5.x branch June 27, 2018 07:12
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.

1 participant