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 #175

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 29, 2018

This PR contains the following updates:

Package Type Update Change References
mocha devDependencies major 2.3.0 -> 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

v3.5.3

Compare Source

🐛 Fixes

v3.5.2

Compare Source

🐛 Fixes

v3.5.1

Compare Source

📰 News

  • 📣 Mocha is now sponsoring PDXNode! If you're in the Portland area, come check out the monthly talks and hack nights!

🐛 Fixes

🔩 Other

v3.5.0

Compare Source

📰 News

  • Mocha now has a code of conduct (thanks @​kungapal!).
  • Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.
  • WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!

🔒 Security Fixes

🎉 Enhancements

🔩 Other

v3.4.2

Compare Source

🐛 Fixes

🔩 Other

v3.4.1

Compare Source

Fixed a publishing mishap with git's autocrlf settings.

v3.3.0

Compare Source

Thanks to all our contributors, maintainers, sponsors, and users! ❤️

As highlights:

  • We've got coverage now!
  • Testing is looking less flaky \o/.
  • No more nitpicking about "mocha.js" build on PRs.

🎉 Enhancements

🐛 Fixes

🔍 Coverage

🔩 Other

v3.2.0

Compare Source

📰 News

Mocha is now a JS Foundation Project!

Mocha is proud to have joined the JS Foundation. For more information, read the announcement.

Contributor License Agreement

Under the foundation, all contributors to Mocha must sign the JS Foundation CLA before their code can be merged. When sending a PR--if you have not already signed the CLA--a friendly bot will ask you to do so.

Mocha remains licensed under the MIT license.

🐛 Bug Fix

🎉 Enhancement

🔩 Other

Thanks to all our contributors, sponsors and backers! Keep on the lookout for a public roadmap and new contribution guide coming soon.

v3.1.2

Compare Source

🐛 Bug Fix

v3.1.1

Compare Source

🐛 Bug Fix

🔩 Other

v3.1.0

Compare Source

🎉 Enhancement

🐛 Bug Fix

v3.0.2

Compare Source

🐛 Bug Fix

v3.0.1

Compare Source

🐛 Bug Fix

v3.0.0

Compare Source

💥 Breaking Changes

  • ⚠️ Due to the increasing difficulty of applying security patches made within its dependency tree, as well as looming incompatibilities with Node.js v7.0, Mocha no longer supports Node.js v0.8.

  • ⚠️ Mocha may no longer be installed by versions of npm less than 1.4.0. Previously, this requirement only affected Mocha's development dependencies. In short, this allows Mocha to depend on packages which have dependencies fixed to major versions (^).

  • .only() is no longer "fuzzy", can be used multiple times, and generally just works like you think it should. 😂

  • To avoid common bugs, when a test injects a callback function (suggesting asynchronous execution), calls it, and returns a Promise, Mocha will now throw an exception:

    ```js
    const assert = require('assert');

    it('should complete this test', function (done) {
    return new Promise(function (resolve) {
    assert.ok(true);
    resolve();
    })
    .then(done);
    });
    ```

    The above test will fail with Error: Resolution method is overspecified. Specify a callback *or* return a Promise; not both..

  • When a test timeout value greater than 2147483648 is specified in any context (--timeout, mocha.setup(), per-suite, per-test, etc.), the timeout will be disabled and the test(s) will be allowed to run indefinitely. This is equivalent to specifying a timeout value of 0. See MDN for reasoning.

  • The dot reporter now uses more visually distinctive characters when indicating "pending" and "failed" tests.

  • Mocha no longer supports component.

  • The long-forsaken HTMLCov and JSONCov reporters--and any relationship to the "node-jscoverage" project--have been removed.

  • spec reporter now omits leading carriage returns (\r) in non-TTY environment.

🎉 Enhancements

🐛 Bug Fixes

🔩 Other

We ❤️ our backers and sponsors!

:shipit:

v2.5.3

Compare Source

v2.5.2

Compare Source

v2.5.1

Compare Source

Thanks @​entertainyou, @​SimenB, @​just-paja for the heads-up.

v2.4.5

Compare Source

v2.4.4

Compare Source

v2.4.3

Compare Source

v2.4.2

Compare Source

v2.4.1

Compare Source

v2.3.4

Compare Source

  • Update debug dependency to 2.2.0
  • remove duplication of mocha.opts on process.argv
  • Fix typo in test/reporters/nyan.js

v2.3.3

Compare Source

v2.3.2

Compare Source

v2.3.1

Compare Source

  • #​1812 - Fix: Bail flag causes before() hooks to be run even after a failure ([@​aaroncrows])

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.

@codecov
Copy link

codecov bot commented Dec 29, 2018

Codecov Report

Merging #175 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #175   +/-   ##
=======================================
  Coverage   30.78%   30.78%           
=======================================
  Files          33       33           
  Lines         393      393           
  Branches       64       64           
=======================================
  Hits          121      121           
  Misses        272      272

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7bbc286...37a01f2. Read the comment docs.

1 similar comment
@codecov
Copy link

codecov bot commented Dec 29, 2018

Codecov Report

Merging #175 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #175   +/-   ##
=======================================
  Coverage   30.78%   30.78%           
=======================================
  Files          33       33           
  Lines         393      393           
  Branches       64       64           
=======================================
  Hits          121      121           
  Misses        272      272

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7bbc286...37a01f2. Read the comment docs.

@jameswlane jameswlane closed this Jan 19, 2019
@renovate
Copy link
Author

renovate bot commented Jan 19, 2019

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@renovate renovate bot deleted the renovate/mocha-5.x branch January 19, 2019 18:17
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.

2 participants