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 - autoclosed #8

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 18, 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

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:

    ```js
    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

📖 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
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

👎 Deprecations

🎉 Enhancements

📖 Documentation

🔩 Other


Renovate configuration

📅 Schedule: At any time (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.


  • If you want to rebase/retry this PR, check this box

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

@renovate renovate bot force-pushed the renovate/mocha-5.x branch 3 times, most recently from 7be5caf to b655beb Compare March 7, 2018 17:38
@renovate renovate bot force-pushed the renovate/mocha-5.x branch 2 times, most recently from e84a76e to 917926b Compare April 18, 2018 17:34
@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 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 changed the title chore(deps): update dependency mocha to v5 Update dependency mocha to v5 Jun 7, 2018
@renovate renovate bot changed the title Update dependency mocha to v5 chore(deps): update dependency mocha to v5 Jun 7, 2018
@renovate renovate bot force-pushed the renovate/mocha-5.x branch 2 times, most recently from f3e526b to 043e265 Compare September 11, 2018 07:23
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5 chore(deps): update dependency mocha to v5 - autoclosed Feb 18, 2019
@renovate renovate bot closed this Feb 18, 2019
@renovate renovate bot deleted the renovate/mocha-5.x branch February 18, 2019 21:28
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