Skip to content

Conversation

@terraharbor-renovator
Copy link
Contributor

@terraharbor-renovator terraharbor-renovator bot commented Sep 14, 2025

This PR contains the following updates:

Package Change Age Confidence
@types/react (source) 19.1.12 -> 19.2.0 age confidence
@types/react-dom (source) 19.1.9 -> 19.2.0 age confidence
react (source) 19.1.1 -> 19.2.0 age confidence
react-dom (source) 19.1.1 -> 19.2.0 age confidence

Release Notes

facebook/react (react)

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

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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@terraharbor-renovator terraharbor-renovator bot added priority: soon renovate state: pending Pending requirements, dependencies, data, or more information type: chore Converting measurements, reorganizing folder structure, and less impactful tasks work: obvious The situation is obvious, best practices used labels Sep 14, 2025
@terraharbor-renovator terraharbor-renovator bot requested review from a team as code owners September 14, 2025 03:28
@terraharbor-renovator terraharbor-renovator bot added priority: soon work: obvious The situation is obvious, best practices used renovate state: pending Pending requirements, dependencies, data, or more information type: chore Converting measurements, reorganizing folder structure, and less impactful tasks labels Sep 14, 2025
@terraharbor-renovator terraharbor-renovator bot changed the title chore(deps): update dependency @types/react to v19.1.13 chore(deps): update dependency @types/react to v19.1.14 Sep 28, 2025
@terraharbor-renovator terraharbor-renovator bot force-pushed the renovate-github/react-monorepo branch from c8cbebc to e2ba3d7 Compare September 28, 2025 03:35
@terraharbor-renovator terraharbor-renovator bot force-pushed the renovate-github/react-monorepo branch from e2ba3d7 to 25627db Compare October 5, 2025 03:33
@terraharbor-renovator terraharbor-renovator bot changed the title chore(deps): update dependency @types/react to v19.1.14 chore(deps): update react monorepo to v19.2.0 Oct 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: soon renovate state: pending Pending requirements, dependencies, data, or more information type: chore Converting measurements, reorganizing folder structure, and less impactful tasks work: obvious The situation is obvious, best practices used

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant