build(deps-dev): bump mocha from 11.7.6 to 11.8.0

[dependabot]

Bumps mocha from 11.7.6 to 11.8.0.

Release notes

Sourced from mocha's releases.

v11.8.0

11.8.0 (2026-08-02)

🌟 Features

• add --fail-hook-affected-tests option to report skipped tests as failed (#5519) (#6052) (7830309)

🧹 Chores

• add modern Netlify to v11.x branch (#6082) (26deb23), closes #5696
• change site title to Mocha 11, update index note (#6086) (1f44d5f)
• CI: bump Node from 22 to 24 in publish action (#6206) (05aec43)

v11.7.7

11.7.7 (2026-06-13)

🩹 Fixes

• surface ts-node compile errors (#6045) (3477563)

Changelog

Sourced from mocha's changelog.

11.8.0 (2026-08-02)

🌟 Features

• add --fail-hook-affected-tests option to report skipped tests as failed (#5519) (#6052) (7830309)

🧹 Chores

• add modern Netlify to v11.x branch (#6082) (26deb23), closes #5696
• change site title to Mocha 11, update index note (#6086) (1f44d5f)
• CI: bump Node from 22 to 24 in publish action (#6206) (05aec43)

11.7.7 (2026-06-13)

🩹 Fixes

• surface ts-node compile errors (#6045) (3477563)

Commits

• 90c1bb3 chore(v11.x): release 11.8.0 (#6076)
• 05aec43 chore(CI): bump Node from 22 to 24 in publish action (#6206)
• 1f44d5f chore: change site title to Mocha 11, update index note (#6086)
• 26deb23 chore: add modern Netlify to v11.x branch (#6082)
• 7830309 feat: add --fail-hook-affected-tests option to report skipped tests as failed...
• 41f2b95 chore(v11.x): release 11.7.7 (#6068)
• 3477563 fix: surface ts-node compile errors (#6045)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​mocha@​11.7.6 ⏵ 11.8.0			+1	+2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/mocha@11.8.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report