[Snyk] Security upgrade mocha from 11.7.5 to 12.0.0

[sestinj]

Snyk has created this PR to fix 4 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• extensions/vscode/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18313044	756
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18512280	756
	Infinite loop SNYK-JS-BRACEEXPANSION-15789759	649
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650	649

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[sestinj]

This major version upgrade of Mocha introduces several breaking changes, primarily related to the supported runtime environment.

Breaking Changes:

• Node.js Support: The minimum required Node.js version has been increased from 18.18.0 to ^20.19.0 || >=22.12.0. Projects running on older Node.js versions will need to upgrade their environment.
• Browser Support: The minimum supported browser versions have been updated to those that were stable as of April 2023 (e.g., Chrome 112, Firefox 112, Safari 16.4).
• Default Behavior Change: The --forbid-only flag now defaults to true in CI environments (when the CI environment variable is set). This will cause builds to fail if .only() is used in tests, which is a common practice during development.

Recommendation:
Verify that your CI and local development environments meet the new Node.js version requirements. Review your test suites to ensure no .only() calls are committed, or explicitly set --forbid-only=false in your CI test script if needed.

Source: Mocha v12 Release Plan

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.