chore(deps): update dependency eslint to v9

renovate-bot commented 5 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	`8.57.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 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 has been generated by Mend Renovate. View repository job log here.

forking-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: web-app-demo/Frontend/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular-eslint/builder@17.2.1
npm ERR! Found: eslint@9.0.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"9.0.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@6.19.0
npm ERR!     node_modules/@angular-eslint/eslint-plugin/node_modules/@typescript-eslint/utils
npm ERR!       @typescript-eslint/utils@"6.19.0" from @angular-eslint/eslint-plugin@17.2.1
npm ERR!       node_modules/@angular-eslint/eslint-plugin
npm ERR!         dev @angular-eslint/eslint-plugin@"17.2.1" from the root project
npm ERR!         1 more (@angular-eslint/schematics)
npm ERR!     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@6.19.0
npm ERR!     node_modules/@angular-eslint/eslint-plugin-template/node_modules/@typescript-eslint/utils
npm ERR!       @typescript-eslint/utils@"6.19.0" from @angular-eslint/eslint-plugin-template@17.2.1
npm ERR!       node_modules/@angular-eslint/eslint-plugin-template
npm ERR!         dev @angular-eslint/eslint-plugin-template@"17.2.1" from the root project
npm ERR!         1 more (@angular-eslint/schematics)
npm ERR!       1 more (@typescript-eslint/type-utils)
npm ERR!     3 more (@typescript-eslint/utils, @typescript-eslint/utils, eslint)
npm ERR!   1 more (eslint-config-google)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.20.0 || ^8.0.0" from @angular-eslint/builder@17.2.1
npm ERR! node_modules/@angular-eslint/builder
npm ERR!   dev @angular-eslint/builder@"17.2.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@8.57.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^7.20.0 || ^8.0.0" from @angular-eslint/builder@17.2.1
npm ERR!   node_modules/@angular-eslint/builder
npm ERR!     dev @angular-eslint/builder@"17.2.1" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-11T19_37_28_463Z-eresolve-report.txt

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

gcf-merge-on-green[bot] commented 5 months ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

forking-renovate[bot] commented 5 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.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.

GoogleCloudPlatform / document-ai-samples