chore(deps): update dependency @smartive/eslint-config to v9 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@smartive/eslint-config	7.0.3 → 9.0.5

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

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

v9.0.5

Compare Source

Bug Fixes

• disable import-x/no-named-as-default (#​170) (7fd2761)

v9.0.4

Compare Source

Bug Fixes

• disable import-x/no-rename-default (#​169) (d59ac69)

v9.0.3

Compare Source

Bug Fixes

• restore the import-x/resolver-next setting (#​166) (3f2941c), closes #​164

v9.0.2

Compare Source

Bug Fixes

• switch back to legacy resolver for import-x in order to fix OOM issues (#​164) (f89026e)

v9.0.1

Compare Source

Bug Fixes

• initialize the import-x resolver in the nextjs rule set (#​160) (eff8fdc)

v9.0.0

Compare Source

• feat!: add @​stylistic/eslint-plugin (a21e9a0)
• feat(forbid-component-props)!: report as an error instead of a warning (#​158) (bb99390)
• feat(plugin)!: rename the rule namespace to [@smartive-eslint](https://redirect.github.com/smartive-eslint) (#​156) (2373a57)

BREAKING CHANGES

• @stylistic/eslint-plugin is now a dependency with three of its rules enabled
  as error: jsx-curly-brace-presence, jsx-self-closing-comp, jsx-pascal-case

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

• @smartive-eslint/forbid-component-props reports as error
  rather than warn. Lint runs that passed with these warnings now fail. To keep
  the previous behaviour, set it back in your own config:
  '@smartive-eslint/forbid-component-props': ['warn', { forbid: ['style', 'className'] }].

Co-authored-by: Claude Opus 5 (1M context) noreply@anthropic.com

• The smartive plugin namespace is now @smartive-eslint.
  Rename smartive/forbid-component-props to
  @smartive-eslint/forbid-component-props in every rule override and
  eslint-disable comment. An override that sets the rule to off under the old
  namespace is silently ignored rather than reported, so it must be found by
  searching rather than by running ESLint.

Co-authored-by: Claude Opus 5 (1M context) noreply@anthropic.com

v8.1.1

Compare Source

Bug Fixes

• initialize the import-x resolver in the nextjs rule set (8.x) (#​161) (8df751e)

v8.1.0

Compare Source

Features

• forbid-component-props: support per-prop allow lists (#​153) (d9d481a)

v8.0.0

Compare Source

• feat!: replace eslint-plugin-react, -react-hooks and -import (#​134) (d15a13c), closes vercel/next.js#89764

Bug Fixes

• declare @​eslint/js as a runtime dependency (#​141) (bb4a372)
• eslint-plugin-react not working in ESLint v10 (#​101) (bc4ee66)

Documentation

• note the rules newly enforced by the ESLint React preset (#​142) (3f0beec)

Features

• add support for ESLint v10 (#​100) (fbcc1ec)

BREAKING CHANGES

• the ESLint React preset enforces 44 checks that had no equivalent in
  the previous rule sets, 14 of them as errors, so projects that linted clean on 7.x will
  report new problems without any source change. See "Upgrading from v7" in the README.
• requires ESLint 10.0.0 or newer, and rule ids change, so
  eslint-disable comments naming react/*, react-hooks/* or import/* rules need
  updating.

---

Configuration

📅 Schedule: (UTC)

• 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 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: package-lock.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @smartive/utils@1.0.0
npm error Found: eslint@9.39.5
npm error node_modules/eslint
npm error   dev eslint@"9.39.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^10.0.0" from @smartive/eslint-config@9.0.5
npm error node_modules/@smartive/eslint-config
npm error   dev @smartive/eslint-config@"9.0.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-30T07_35_25_187Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-30T07_35_25_187Z-debug-0.log