Skip to content
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

Update dependency mocha to v10 -- #1365

Closed
wants to merge 1 commit into from

Conversation

devmobileph
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
mocha (source) devDependencies major ^9.2.2 -> ^10.0.0

Release Notes

mochajs/mocha

v10.0.0

Compare Source

💥 Breaking Changes

🔩 Other

Also thanks to @​ea2305 and @​SukkaW for improvements to our documentation.


Configuration

📅 Schedule: "after 9am and before 4pm on Wednesday" in timezone Europe/Amsterdam.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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, click this checkbox.

This PR has been generated by Renovate Bot.

@devmobileph
Copy link
Contributor Author

devmobileph commented May 4, 2022

⚠ 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 could not resolve
npm ERR! 
npm ERR! While resolving: ts-mocha@9.0.2
npm ERR! Found: mocha@10.0.0
npm ERR! node_modules/mocha
npm ERR!   dev mocha@"^10.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mocha@"^3.X.X || ^4.X.X || ^5.X.X || ^6.X.X || ^7.X.X || ^8.X.X || ^9.X.X" from ts-mocha@9.0.2
npm ERR! node_modules/ts-mocha
npm ERR!   dev ts-mocha@"^9.0.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mocha@9.2.2
npm ERR! node_modules/mocha
npm ERR!   peer mocha@"^3.X.X || ^4.X.X || ^5.X.X || ^6.X.X || ^7.X.X || ^8.X.X || ^9.X.X" from ts-mocha@9.0.2
npm ERR!   node_modules/ts-mocha
npm ERR!     dev ts-mocha@"^9.0.2" 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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2022-05-04T14_03_22_509Z-debug-0.log

@BCaspari
Copy link
Contributor

BCaspari commented May 4, 2022

ts mocha does not support mocha 10 yet: piotrwitek/ts-mocha#77

@devmobileph devmobileph force-pushed the auto-dep-update/mocha-10.x branch 3 times, most recently from d65c939 to 006d573 Compare May 4, 2022 10:07
@BCaspari BCaspari closed this May 5, 2022
@BCaspari BCaspari deleted the auto-dep-update/mocha-10.x branch May 5, 2022 05:32
@devmobileph
Copy link
Contributor Author

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 10.x releases. However, if you upgrade to 10.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@BCaspari BCaspari changed the title Update dependency mocha to v10 Update dependency mocha to v10 -- May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants