chore(deps): update dependency eslint-config-prettier to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-prettier	^8.8.0 -> ^9.0.0

---

Release Notes

prettier/eslint-config-prettier (eslint-config-prettier)

v9.0.0

Compare Source

• Added: The CLI helper tool now works with eslint.config.js (flat config). Just like ESLint itself, the CLI tool automatically first tries eslint.config.js and then eslintrc, and you can force which one to use by setting the [ESLINT_USE_FLAT_CONFIG] environment variable. Note that the config of eslint-config-prettier has always been compatible with eslint.config.js (flat config) – it was just the CLI tool that needed updating. On top of that, the docs have been updated to mention how to use both eslint.config.js (flat config) and eslintrc, and the tests now test both config systems.
• Changed: [unicode-bom] is no longer turned off. Prettier preserves the BOM if you have one, and does not add one if missing. It was wrong of eslint-config-prettier to disable that rule. If you get ESLint errors after upgrading, either add "unicode-bom": "off" to your config to disable it again, or run ESLint with --fix to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@​nstepien)!

v8.10.0

Compare Source

• Added: [max-statements-per-line]. Thanks to @​Zamiell!

v8.9.0

Compare Source

• Added: [vue/array-element-newline]. Thanks to @​xcatliu!

---

Configuration

📅 Schedule: Branch creation - "on the first day of the week" in timezone Asia/Tokyo, 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]

⚠ 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: pnpm-lock.yaml

[10:09:38.523] INFO (9): Installing tool node v20.9.0...
v20.9.0
10.1.0
0.20.0
[10:09:41.443] INFO (9): Installed tool node in 2.9s.
[10:09:41.768] INFO (52): Installing tool pnpm v8.10.0...
8.10.0
[10:09:43.375] INFO (52): Installed tool pnpm in 1.6s.
Progress: resolved 1, reused 0, downloaded 0, added 0
 WARN  GET https://registry.npmjs.org/next/-/next-13.5.0.tgz error (ERR_PNPM_FETCH_404). Will retry in 10 seconds. 2 retries left.
Progress: resolved 25, reused 0, downloaded 25, added 0
 WARN  GET https://registry.npmjs.org/next/-/next-13.5.0.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.
undefined
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/next/-/next-13.5.0.tgz: Not Found - 404

No authorization header was set for the request.