[Snyk] Security upgrade mocha from 7.2.0 to 10.1.0

[leonardoadame]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • tools/node_modules/eslint/node_modules/glob-parent/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	479/1000 Why? Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818	Yes	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-JS-MOCHA-2863123	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: mocha

The new version differs by 250 commits.

• 5f96d51 build(v10.1.0): release
• ed74f16 build(v10.1.0): update CHANGELOG
• 51d4746 chore(devDeps): update 'ESLint' to v8 (Problem with build Node v0.10.x on ARM Linux nodejs/node#4926)
• 4e06a6f fix(browser): increase contrast for replay buttons (Wrong exception reported for throw with toString returning symbol nodejs/node#4912)
• 41567df Support prefers-color-scheme: dark (Shared library issues for nodejs V5.5.0 on Solaris x86 11.2 and 11.3 nodejs/node#4896)
• 61b4b92 fix the regular expression for function `clean` in `utils.js` (Feature Request: get current response headers or unset them alll nodejs/node#4770)
• 77c18d2 chore: use standard 'Promise.allSettled' instead of polyfill (Node crashes when a big sparse array is given to console.log (might cause DoS) nodejs/node#4905)
• 84b2f84 chore(ci): upgrade GH actions to latest versions (Cannot build msi nodejs/node#4899)
• 023f548 build(v10.0.0): release
• 62b1566 build(v10.0.0): update CHANGELOG
• fbe7a24 chore: update dependencies (SNICallback doesn't appear to work with tls.createSecurePair() nodejs/node#4878)
• 2b98521 docs: replace 'git.io' short links (Clarify Buffer hex string error message nodejs/node#4877) [ci skip]
• 007fa65 chore(ci): add Node v18 to test matrix (doc: keep the names in sorted order nodejs/node#4876)
• f6695f0 chore(esm): remove code for Node v12 (src: attach error to stack on displayErrors nodejs/node#4874)
• 59f6192 chore(ci): conditionally skip 'push' event (deps: upgrade to npm 2.14.15 nodejs/node#4872)
• b863359 docs: fix 'fgrep' url (doc: make Buffer documentation styles consistent nodejs/node#4873)
• baaa41a chore(ci): ignore changes to docs files (doc: fix JSON generation for aliased methods nodejs/node#4871)
• ac81cc5 refactor!: drop support of 'growl' notification (doc: make doctool support guides nodejs/node#4866)
• 3946453 chore(deps)!: upgrade 'minimatch' (octane benchmark faults on ppc64le nodejs/node#4865)
• 592905b refactor!: rename 'bin/mocha' to 'bin/mocha.js' (doc: fix nonsensical grammar in Buffer::write nodejs/node#4863)
• b7b849b refactor!: remove deprecated Runner signature (test: fs.link() test runs on same device nodejs/node#4861)
• 0608fa3 chore(site): fix supporters' download (test: fs.link() on same device nodejs/node#4859)
• 785aeb1 chore(test): drop AMD/'requirejs' (OpenSSL upgrades: January 28th 2016 nodejs/node#4857)
• ed640c4 chore(devDeps): upgrade 'coffee-script' (Proposal: canary/next/master release strategy nodejs/node#4856)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ccd48da

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR