Skip to content

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

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 26, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-mocha 10.5.0 -> 11.1.0 age adoption passing confidence

Release Notes

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

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
Code Refactoring
Build-Related
  • Use packtory as a release tool (#​374)
  • Update CI matrix to use latest node versions (#​370)

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 4 times, most recently from 4b48bac to d925824 Compare May 1, 2025 22:41
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 9 times, most recently from 3976dec to 22184fc Compare May 9, 2025 10:52
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 8 times, most recently from e498dbb to 9601619 Compare May 20, 2025 23:06
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 2 times, most recently from 44711e7 to 8075dd2 Compare May 24, 2025 11:28
Copy link
Contributor Author

renovate bot commented May 24, 2025

⚠️ 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: @pact-foundation/pact@15.0.1
npm ERR! Found: eslint@8.57.1
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"8.57.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=9.0.0" from eslint-plugin-mocha@11.1.0
npm ERR! node_modules/eslint-plugin-mocha
npm ERR!   dev eslint-plugin-mocha@"11.1.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/2025-07-02T22_59_54_384Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 6 times, most recently from e93f3f3 to 7bb3800 Compare May 29, 2025 00:57
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 3 times, most recently from 67c53d1 to abd4920 Compare May 31, 2025 09:07
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 7 times, most recently from 1f6b33a to aaed53a Compare June 13, 2025 19:31
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 5 times, most recently from 52e0a35 to 200ef17 Compare June 23, 2025 15:34
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch 9 times, most recently from 2878e92 to 19594ab Compare June 27, 2025 12:36
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch from 19594ab to f044387 Compare July 2, 2025 02:54
@renovate renovate bot force-pushed the renovate/eslint-plugin-mocha-11.x branch from f044387 to 8dcdc69 Compare July 2, 2025 22:59
@mefellows mefellows closed this Jul 6, 2025
@mefellows mefellows deleted the renovate/eslint-plugin-mocha-11.x branch July 6, 2025 22:22
Copy link
Contributor Author

renovate bot commented Jul 6, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 11.x releases. But if you manually upgrade to 11.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

1 participant