Skip to content

chore(deps): update react monorepo (major) - #1053

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 Aug 7, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@types/react (source) 18.3.31 → 19.3.0 age confidence
@types/react-dom (source) 18.3.7 → 19.3.0 age confidence
eslint-plugin-react-hooks (source) 5.2.0 → 7.1.1 age confidence
react (source) 18.3.1 → 19.3.0 age confidence
react-dom (source) 18.3.1 → 19.3.0 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.

react/react (react)

v19.3.0

Compare Source

New React Features
New React DOM Features
  • browser(): a new react-dom API that returns a usable which errors during server rendering and resolves in the browser. use(browser()) inside a <Suspense> boundary marks a subtree as browser-only without reporting a recoverable error (@​gnoff: #​37143, #​37241)
    • Added an onBrowserBailout option to the react-dom/server APIs to observe when a subtree defers to the browser (@​gnoff #​37193)
Notable changes
All Changes
React
React DOM
React Server
React Server Components

v19.2.9: 19.2.9 (October 14th, 2026)

Compare Source

React Server Components

v19.2.8: 19.2.8 (July 21st, 2026)

Compare Source

React Server Components

v19.2.7

Compare Source

React Server Components

v19.2.6

Compare Source

React Server Components

v19.2.5

Compare Source

React Server Components

v19.2.4

Compare Source

React Server Components

v19.2.3

Compare Source

React Server Components

v19.2.2

Compare Source

React Server Components

v19.2.1

Compare Source

React Server Components

v19.2.0

Compare Source

Below is a list of all new features, APIs, and bug fixes.

Read the [React 19.2 release post](https:

[!IMPORTANT]
✂ PR body was truncated to here.


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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 Aug 7, 2026
@renovate

renovate Bot commented Aug 7, 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@6.0.0
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@6.0.0
npm error node_modules/@terrestris/eslint-config-typescript-react
npm error   dev @terrestris/eslint-config-typescript-react@"6.0.0" 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@6.0.0
npm error   node_modules/@terrestris/eslint-config-typescript-react
npm error     dev @terrestris/eslint-config-typescript-react@"6.0.0" 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-13T17_48_56_496Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-13T17_48_56_496Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 8d4d7bf to 80784c8 Compare August 14, 2026 04:02
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 8b5ab58 to 21d1a8b Compare August 27, 2026 23:51
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 6d1bc9a to ec76d90 Compare September 7, 2026 23:27
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 608d01b to b1b7086 Compare September 15, 2026 15:08
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from f3807a4 to f13098e Compare October 1, 2026 20:48
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from f13098e to d4dd4b4 Compare October 4, 2026 13:44
@renovate
renovate Bot force-pushed the renovate/major-react-monorepo branch from d4dd4b4 to 3974c55 Compare October 8, 2026 22:05
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