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.2.0 #73

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 6, 2018

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mocha (source) 5.0.1 -> 5.2.0 age adoption passing confidence

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 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 Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency mocha to v5.0.2 chore(deps): update dependency mocha to v5.0.3 Mar 7, 2018
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5.0.3 chore(deps): update dependency mocha to v5.0.4 Mar 7, 2018
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5.0.4 chore(deps): update dependency mocha to v5.0.5 Mar 23, 2018
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5.0.5 chore(deps): update dependency mocha to v5.1.0 Apr 12, 2018
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5.1.0 chore(deps): update dependency mocha to v5.1.1 Apr 18, 2018
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5.1.1 Update dependency mocha to v5.1.1 May 9, 2018
@renovate renovate bot changed the title Update dependency mocha to v5.1.1 chore(deps): update dependency mocha to v5.1.1 May 9, 2018
@renovate renovate bot changed the title chore(deps): update dependency mocha to v5.1.1 chore(deps): update dependency mocha to v5.2.0 May 18, 2018
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

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.

None yet

1 participant