Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 4, 2025

This PR contains the following updates:

Package Change Age Confidence
@types/react (source) 19.1.819.2.7 age confidence
react (source) 19.1.019.2.3 age confidence
react-test-renderer (source) 19.1.019.2.3 age confidence

Release Notes

facebook/react (react)

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.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

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
Copy link
Contributor Author

renovate bot commented Aug 4, 2025

⚠️ 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 stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: Keepche@0.0.1
npm error Found: @react-native-firebase/app@22.4.0
npm error node_modules/@react-native-firebase/app
npm error   @react-native-firebase/app@"^22.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @react-native-firebase/app@"21.14.0" from @react-native-firebase/messaging@21.14.0
npm error node_modules/@react-native-firebase/messaging
npm error   @react-native-firebase/messaging@"^21.12.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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/2025-12-31T14_47_27_707Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-31T14_47_27_707Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from d76364f to 93fa028 Compare October 2, 2025 01:32
@renovate renovate bot changed the title fix(deps): update react monorepo fix(deps): update react monorepo to v19.2.0 Oct 2, 2025
@renovate renovate bot changed the title fix(deps): update react monorepo to v19.2.0 fix(deps): update react monorepo Oct 7, 2025
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 93fa028 to f4510ab Compare December 3, 2025 17:55
@renovate renovate bot force-pushed the renovate/react-monorepo branch from f4510ab to 0f411a3 Compare December 11, 2025 22:10
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 0f411a3 to 03442ce Compare December 12, 2025 03:04
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.

1 participant