fix(deps): update dependency eslint to v9 - autoclosed

renovate[bot] commented 5 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	`^8.56.0` -> `^9.0.0`

Release Notes

eslint/eslint (eslint)

### [`v9.0.0`](https://togithub.com/eslint/eslint/compare/v8.57.0...e0cbc50179adac1670f4e0bd9093387a51f4f42a) [Compare Source](https://togithub.com/eslint/eslint/compare/v8.57.0...v9.0.0)

Configuration

📅 Schedule: 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 has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 5 months ago

⚠ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@7.7.1
npm error Found: eslint@9.1.1
npm error node_modules/eslint
npm error   eslint@"^9.0.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@7.7.1
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"7.7.1" from @typescript-eslint/eslint-plugin@7.7.1
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         @typescript-eslint/eslint-plugin@"^7.0.0" from the root project
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.1.1
npm error   1 more (eslint-import-resolver-typescript)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/eslint-plugin@7.7.1
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   @typescript-eslint/eslint-plugin@"^7.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error   peer eslint@"^8.56.0" from @typescript-eslint/eslint-plugin@7.7.1
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     @typescript-eslint/eslint-plugin@"^7.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-04-27T02_36_54_840Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-27T02_36_54_840Z-debug-0.log

vercel[bot] commented 5 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
trident	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 27, 2024 2:39am

yuiseki / TRIDENT