Update dependency eslint-plugin-eslint-plugin to v5.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-eslint-plugin	5.2.1 -> 5.3.0

---

Release Notes

eslint-community/eslint-plugin-eslint-plugin (eslint-plugin-eslint-plugin)

v5.3.0

Compare Source

Features

• add no-property-in-node rule (#​433) (d2b9372)

Documentation

• add another justification for prefer-message-ids rule (#​426) (209d178)

Chores

• add release-please (#​421) (d7331ca)
• config renovate (#​409) (3c845be)
• postprocess with prettier in eslint-doc-generator (#​435) (015c207)
• remove dependentbot.yml infavor of renovate (#​439) (6ae0ee6)
• replace dependency npm-run-all with npm-run-all2 ^5.0.0 (#​427) (062743d)
• update dependency markdownlint-cli to ^0.38.0 (#​410) (6b53c5b)
• update dependency markdownlint-cli to ^0.39.0 (#​431) (f005a2c)

5.2.1 (2023-12-11)

Bug Fixes

• replace context.getScope() with sourceCode.getScope() (6aed8bb)

v5.2.1

Compare Source

v5.2.0

Compare Source

Features

• preparing for eslint v9 (#​400) (35e14cd)

5.1.1 (2023-07-19)

Bug Fixes

• ignore function calls in report-message-format (dea161d)
• ignore SpreadExpressions in no-only-tests and prefer-output-null (4924042)
• use latest ECMAScript version in tests (#​364) (7be0c76)

---

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]

⚠ 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

Scope: all 21 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 29, reused 0, downloaded 20, added 0
Progress: resolved 40, reused 0, downloaded 27, added 0
.                                        |  WARN  deprecated @babel/[email protected]
Progress: resolved 79, reused 0, downloaded 66, added 0
Progress: resolved 129, reused 0, downloaded 116, added 0
Progress: resolved 137, reused 0, downloaded 124, added 0
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @babel/[email protected]
Progress: resolved 153, reused 0, downloaded 140, added 0
packages/next                            |  WARN  deprecated @types/[email protected]
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/third-parties:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/next/-/next-13.5.0.tgz: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/third-parties

No authorization header was set for the request.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: af5668b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR