chore(deps): update pnpm.catalog.default @antfu/eslint-config to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@antfu/eslint-config	^6.7.3 → ^7.6.0

---

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v7.6.0

Compare Source

   🚀 Features

• jsonc: Use jsonc/x language  -  by @​hyoban in #​824 (a9b7a)

   🐞 Bug Fixes

• jsdoc: Separate setup  -  by @​hyoban in #​825 (6742d)

    View changes on GitHub

v7.5.0

Compare Source

   🚀 Features

• markdown: Use markdown language  -  by @​hyoban and @​antfu in #​818 (93063)

    View changes on GitHub

v7.4.3

Compare Source

   🐞 Bug Fixes

• Formating regression  -  by @​antfu (2ef8a)

    View changes on GitHub

v7.4.2

Compare Source

   🐞 Bug Fixes

• Relax eslint peer deps range  -  by @​antfu (b5f53)

    View changes on GitHub

v7.4.1

Compare Source

   🐞 Bug Fixes

• Ignore typescript files when typescript is off  -  by @​antfu (bda75)

    View changes on GitHub

v7.4.0

Compare Source

   🚀 Features

• Angular support  -  by @​St2r and @​antfu in #​804 (67b1b)

   🐞 Bug Fixes

• Update peer dependency requirement for eslint-plugin-react-refresh  -  by @​hyoban in #​813 (19a43)

    View changes on GitHub

v7.3.0

Compare Source

   🚀 Features

• Upgrade eslint-plugin-react-refresh, eslint-plugin-regexp  -  by @​antfu (610e7)
• react: Sync recommend rules  -  by @​hyoban in #​810 (1b870)

   🐞 Bug Fixes

• Use ConfigWithExtends instead of Linter.Config  -  by @​hyoban in #​809 (ad4e5)

    View changes on GitHub

v7.2.0

Compare Source

   🚀 Features

• Upgrade eslint-flat-config-utils, support native extends, close #​800  -  by @​antfu in #​800 (15685)

    View changes on GitHub

v7.1.0

Compare Source

   🚀 Features

• react: Sync recommended config for eslint-plugin-react-refresh  -  by @​hyoban in #​801 (2e029)

    View changes on GitHub

v7.0.1

Compare Source

   🐞 Bug Fixes

• Indent value resolving  -  by @​antfu (0857a)

    View changes on GitHub

v7.0.0

Compare Source

   🚨 Breaking Changes

• Upgrade perfectionist to v5  -  by @​mefengl in #​797 (5878d)

   🚀 Features

• Update all deps  -  by @​antfu (4ac4e)
• react: Enable react/prefer-namespace-import  -  by @​hyoban in #​796 (4ce62)

    View changes on GitHub

---

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 was generated by Mend Renovate. View the repository job log.

[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 20 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 23, reused 0, downloaded 0, added 0
Progress: resolved 32, reused 0, downloaded 0, added 0
Progress: resolved 45, reused 0, downloaded 0, added 0
Progress: resolved 48, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/unjs/unhead/examples/vite-ssr-vue:
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "vite-bundle-analyzer@1.3.2" (possible package takeover)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/unjs/unhead/examples/vite-ssr-vue

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.