chore(deps): update dependency eslint-plugin-mocha to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-mocha	^10.1.0 → ^11.0.0

---

Release Notes

lo1tuma/eslint-plugin-mocha (eslint-plugin-mocha)

v11.3.0

Compare Source

Bug Fixes

• fix: don't add loops to current layer in consistent-spacing-between-b… (#​408)
• Fix type of the plugin object's configs field (#​393)
• Fix handling of suites in no-synchronous-tests (#​401)

Enhancements

• Fix: disallow extra properties in rule options (#​395)
• Improve exported plugin type (#​400)

Documentation

• Syntax highlighting for return in no-synchronous-tests-return (#​402)

Build-Related

• ci: drop node 23, add node 24 (#​397)

v11.2.0

Compare Source

Enhancements

• Improve exported plugin type (#​400)

Build-Related

• ci: drop node 23, add node 24 (#​397)

v11.1.0

Compare Source

Bug Fixes

• Fix detecting mocha config calls in no-setup-in-describe (#​387)
• Fix consistent-spacing-between-blocks when using timeout() modifier (#​379)

Enhancements

• Include typescript declaration files in npm package (#​378)

Documentation

• Fix valid-suite-title options documentation (#​385)

Code Refactoring

• Add test to verify no-identical-title supports same titles in different suites (#​388)
• Add test-case to verify generated tests work with consistent-spacing-between-blocks (#​386)
• Add regression tests for no-setup-in-describe (#​380)

v11.0.0

Compare Source

Breaking Changes

• Rename *-description rules to *-title (#​369)
• Rename no-async-describe to no-async-suite (#​368)
• Drop support for commonjs in no-exports rule (#​366)
• Implement new resolve algorithm (#​365)
• Switch to ESM (#​362)
• Stop supporting ESLint versions < 9 (#​359)
• Remove support for node v14, v16 and v18 (#​345)

Features

• Implement new rule consistent-interface (#​367)

Enhancements

• Add name to flat configs (#​356)

Dependency Upgrades

• Update dependencies (#​371)
• Update all dependencies (#​360)

Code Refactoring

• Migrate codebase to typescript (#​372)
• Replace nyc with c8 for collecting coverage information (#​361)
• Use @​eslint-community/eslint-utils instead of unmaintained eslint-utils (#​358)
• Use node builtin assert instead of chai (#​357)

Build-Related

• Use packtory as a release tool (#​374)
• Update CI matrix to use latest node versions (#​370)

---

Configuration

📅 Schedule: (UTC)

• 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: loopback-connector-rest@7.0.1
npm ERR! Found: eslint@8.57.1
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^8.27.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=9.0.0" from eslint-plugin-mocha@11.3.0
npm ERR! node_modules/eslint-plugin-mocha
npm ERR!   dev eslint-plugin-mocha@"^11.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-16T17_10_34_204Z-debug-0.log