Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 28, 2025

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-react-hooks (source) 5.1.05.2.0 age confidence
react (source) 19.0.019.2.4 age confidence
react-dom (source) 19.0.019.2.4 age confidence

Release Notes

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

v5.2.0

Compare Source

facebook/react (react)

v19.2.4: 19.2.4 (January 26th, 2026)

Compare Source

React Server Components

v19.2.3: 19.2.3 (December 11th, 2025)

Compare Source

React Server Components

v19.2.2: 19.2.2 (December 11th, 2025)

Compare Source

React Server Components

v19.2.1: 19.2.1 (December 3rd, 2025)

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 for more information.

New React Features
  • <Activity>: A new API to hide and restore the UI and internal state of its children.
  • useEffectEvent is a React Hook that lets you extract non-reactive logic into an Effect Event.
  • cacheSignal (for RSCs) lets your know when the cache() lifetime is over.
  • React Performance tracks appear on the Performance panel’s timeline in your browser developer tools
New React DOM Features
  • Added resume APIs for partial pre-rendering with Web Streams:
  • Added resume APIs for partial pre-rendering with Node Streams:
  • Updated prerender APIs to return a postponed state that can be passed to the resume APIs.
Notable changes
  • React DOM now batches suspense boundary reveals, matching the behavior of client side rendering. This change is especially noticeable when animating the reveal of Suspense boundaries e.g. with the upcoming <ViewTransition> Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.
  • Add Node Web Streams (prerender, renderToReadableStream) to server-side-rendering APIs for Node.js
  • Use underscore instead of : IDs generated by useId
All Changes
React
React DOM
React Server Components
React Reconciler

v19.1.5: 19.1.5 (January 26th, 2026)

Compare Source

React Server Components

v19.1.4: 19.1.4 (December 11th, 2025)

Compare Source

React Server Components

v19.1.3: 19.1.3 (December 11th, 2025)

Compare Source

React Server Components

v19.1.2: 19.1.2 (December 3rd, 2025)

Compare Source

React Server Components

v19.1.1

Compare Source

React

v19.1.0

Compare Source

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #​29923, #​32353, #​30306,
    #​32538, #​32529, #​32538
React
  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #​32069, #​32163, #​32224, #​32252
  • Reduced unnecessary client rendering through improved hydration scheduling #​31751
  • Increased priority of client rendered Suspense boundaries #​31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #​31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #​31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #​31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #​32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #​32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #​32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #​32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Compiler and bindings #​31808
  • Improve passive effect scheduling for consistent task yielding. #​31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #​32528
  • Fixed component name resolution for Portal #​32640
  • Added support for beforetoggle and toggle events on the dialog element. #​32479
React DOM
  • Fixed double warning when the href attribute is an empty string #​31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #​32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #​32250
  • Added support for <script> and <template> tags to be nested within <select> tags. #​31837
  • Fixed responsive images to be preloaded as HTML instead of headers #​32445
use-sync-external-store
  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #​25231
React Server Components
  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #​31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #​31840, #​31851
  • Fixed an issue where pending chunks were counted twice. #​31833
  • Added support for streaming in edge environments #​31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #​32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #​31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #​32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #​31725, #​32132, #​31799, #​32294, #​31741

v19.0.4: 19.0.4 (January 26th, 2026)

Compare Source

React Server Components

v19.0.3: 19.0.3 (December 11th, 2025)

Compare Source

React Server Components

v19.0.2: 19.0.2 (December 11th, 2025)

Compare Source

React Server Components

v19.0.1: 19.0.1 (December 3rd, 2025)

Compare Source

React Server Components

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.

👻 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 force-pushed the renovate/react-monorepo branch 2 times, most recently from 8d69e56 to 93e77ba Compare March 13, 2025 19:15
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 93e77ba to 2c52a58 Compare March 28, 2025 21:57
@renovate renovate bot changed the title chore(deps): update dependency eslint-plugin-react-hooks to v5.2.0 fix(deps): update react monorepo Mar 28, 2025
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 2c52a58 to f192d07 Compare April 8, 2025 11:08
@renovate renovate bot force-pushed the renovate/react-monorepo branch from f192d07 to 2ac055a Compare April 24, 2025 10:54
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 2ac055a to 422d3e9 Compare May 19, 2025 19:47
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from f718578 to 8d288e5 Compare June 4, 2025 06:36
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 8d288e5 to ee3b8cf Compare June 22, 2025 13:28
@renovate renovate bot force-pushed the renovate/react-monorepo branch from ee3b8cf to 6257448 Compare July 28, 2025 18:34
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 6257448 to 9f2b5f4 Compare August 10, 2025 14:34
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 9f2b5f4 to fbb9f4d Compare August 19, 2025 13:32
@renovate renovate bot force-pushed the renovate/react-monorepo branch from fbb9f4d to ef41e2c Compare September 25, 2025 15:58
@renovate renovate bot changed the title fix(deps): update react monorepo chore(deps): update react monorepo Sep 25, 2025
@renovate renovate bot force-pushed the renovate/react-monorepo branch from ef41e2c to 8869897 Compare October 1, 2025 21:56
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 8869897 to 1135638 Compare November 11, 2025 01:08
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 1135638 to bb73b78 Compare November 18, 2025 12:34
@renovate renovate bot force-pushed the renovate/react-monorepo branch from bb73b78 to a0b7dda Compare December 3, 2025 19:30
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 0c5735b to 7da6901 Compare December 12, 2025 03:07
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 7da6901 to 0389795 Compare December 31, 2025 13:35
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 0389795 to 95d15a0 Compare January 19, 2026 19:13
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 95d15a0 to f3e4442 Compare January 26, 2026 22:00
@renovate renovate bot force-pushed the renovate/react-monorepo branch from f3e4442 to 4fa2d18 Compare February 2, 2026 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants