Skip to content

chore(deps): update dependency eslint-plugin-react-hooks to v7 - #1775

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-react-monorepo
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-react-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jun 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-react-hooks (source) 5.2.0 → 7.1.1 age confidence

Release Notes

facebook/react (eslint-plugin-react-hooks)

v7.1.1

Compare Source

Note: 7.1.0 accidentally removed the component-hook-factories rule, causing errors for users who referenced it in their ESLint config. This is now fixed.

  • Add deprecated no-op component-hook-factories rule for backwards compatibility. (@​mofeiZ in #​36307)

v7.1.0

Compare Source

This release adds ESLint v10 support, improves performance by skipping compilation for non-React files, and includes compiler lint improvements including better set-state-in-effect detection, improved ref validation, and more helpful error reporting.

v7.0.1

Compare Source

v7.0.0

Compare Source

This release slims down presets to just 2 configurations (recommended and recommended-latest), and all compiler rules are enabled by default.

  • Breaking: Removed recommended-latest-legacy and flat/recommended configs. The plugin now provides recommended (legacy and flat configs with all recommended rules), and recommended-latest (legacy and flat configs with all recommended rules plus new bleeding edge experimental compiler rules). (@​poteto in #​34757)

v6.1.1

Compare Source

Note: 6.1.0 accidentally allowed use of recommended without flat config, causing errors when used with ESLint v9's defineConfig() helper. This has been fixed in 6.1.1.

v6.1.0

Compare Source

Note: Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.

  • Breaking: Require Node.js 18 or newer. (@​michaelfaith in #​32458)
  • Breaking: Flat config is now the default recommended preset. Legacy config moved to recommended-legacy. (@​michaelfaith in #​32457)
  • New Violations: Disallow calling use within try/catch blocks. (@​poteto in #​34040)
  • New Violations: Disallow calling useEffectEvent functions in arbitrary closures. (@​jbrown215 in #​33544)
  • Handle React.useEffect in addition to useEffect in rules-of-hooks. (@​Ayc0 in #​34076)
  • Added react-hooks settings config option that to accept additionalEffectHooks that are used across exhaustive-deps and rules-of-hooks rules. (@​jbrown215) in #​34497

v6.0.0

Compare Source

Accidentally released. See 6.1.0 for the actual changes.


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 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 renovate Bot added the renovate label Jun 17, 2026
@renovate

renovate Bot commented Jun 17, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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 could not resolve
npm error
npm error While resolving: @terrestris/eslint-config-typescript-react@5.0.1
npm error Found: eslint-plugin-react-hooks@7.1.1
npm error node_modules/eslint-plugin-react-hooks
npm error   dev eslint-plugin-react-hooks@"7.1.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint-plugin-react-hooks@"^5.1.0" from @terrestris/eslint-config-typescript-react@5.0.1
npm error node_modules/@terrestris/eslint-config-typescript-react
npm error   dev @terrestris/eslint-config-typescript-react@"5.0.1" from the root project
npm error
npm error Conflicting peer dependency: eslint-plugin-react-hooks@5.2.0
npm error node_modules/eslint-plugin-react-hooks
npm error   peer eslint-plugin-react-hooks@"^5.1.0" from @terrestris/eslint-config-typescript-react@5.0.1
npm error   node_modules/@terrestris/eslint-config-typescript-react
npm error     dev @terrestris/eslint-config-typescript-react@"5.0.1" 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-10-04T08_42_39_154Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-04T08_42_39_154Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from a0fcdf7 to 9619488 Compare June 17, 2026 09:35
@renovate renovate Bot changed the title chore(deps): update react monorepo to v7 chore(deps): update react monorepo (major) Jun 22, 2026
@renovate renovate Bot changed the title chore(deps): update react monorepo (major) chore(deps): update dependency eslint-plugin-react-hooks to v7 Jun 25, 2026
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 9619488 to 4b88b13 Compare June 26, 2026 05:43
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from f1febaa to 925b01a Compare July 17, 2026 10:44
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 574b41b to bad9730 Compare July 24, 2026 16:58
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 1de3cf0 to 540ab58 Compare July 30, 2026 14:23
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 95d8535 to e460d87 Compare August 12, 2026 00:08
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from a895651 to 5f2ad45 Compare August 15, 2026 17:26
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from b267832 to 4eca84b Compare September 2, 2026 17:46
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from abc8667 to 1aa7982 Compare September 9, 2026 23:05
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from e8d57f9 to 8bc1250 Compare September 15, 2026 20:49
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 44a853f to 0df754b Compare October 1, 2026 00:12
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from 0df754b to 7fecd99 Compare October 4, 2026 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants