Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 12, 2025

This PR contains the following updates:

Package Change Age Confidence
@storybook/react (source) 8.6.12 -> 8.6.15 age confidence
@testing-library/react 16.3.0 -> 16.3.1 age confidence
@types/react-dom (source) 19.1.3 -> 19.2.3 age confidence
react (source) 19.1.0 -> 19.2.3 age confidence
react-dom (source) 19.1.0 -> 19.2.3 age confidence

Release Notes

storybookjs/storybook (@​storybook/react)

v8.6.15

Compare Source

v8.6.14

Compare Source

v8.6.13

Compare Source

testing-library/react-testing-library (@​testing-library/react)

v16.3.1

Compare Source

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 is behind base branch, 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.

@webteam-app
Copy link
Collaborator

@renovate renovate bot changed the title chore(deps): update dependency @types/react-dom to v19.1.4 chore(deps): update dependency @types/react-dom to v19.1.5 May 13, 2025
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 2 times, most recently from 3a5d046 to cbda3f7 Compare May 16, 2025 04:41
@renovate renovate bot changed the title chore(deps): update dependency @types/react-dom to v19.1.5 chore(deps): update react-ecosystem May 16, 2025
@renovate
Copy link
Contributor Author

renovate bot commented May 16, 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 could not resolve
npm error
npm error While resolving: @canonical/[email protected]
npm error Found: @storybook/[email protected]
npm error node_modules/@storybook/test
npm error   @storybook/test@"8.6.12" from @storybook/[email protected]
npm error   node_modules/@storybook/addon-a11y
npm error     dev @storybook/addon-a11y@"^8.6.12" from the root project
npm error   @storybook/test@"8.6.12" from @storybook/[email protected]
npm error   node_modules/@storybook/addon-interactions
npm error     dev @storybook/addon-interactions@"^8.6.12" from the root project
npm error   1 more (@storybook/react-vite)
npm error
npm error Could not resolve dependency:
npm error dev @storybook/react@"^8.6.12" from the root project
npm error
npm error Conflicting peer dependency: @storybook/[email protected]
npm error node_modules/@storybook/test
npm error   peerOptional @storybook/test@"8.6.15" from @storybook/[email protected]
npm error   node_modules/@storybook/react
npm error     dev @storybook/react@"^8.6.12" 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-17T16_13_35_805Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-17T16_13_35_805Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-ecosystem branch 2 times, most recently from fb5bdb8 to 77babe0 Compare May 20, 2025 14:02
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 3 times, most recently from 5aa54a7 to cf632d7 Compare June 4, 2025 17:02
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 2 times, most recently from 2dec0d5 to f2c9fbd Compare July 29, 2025 14:46
@renovate renovate bot force-pushed the renovate/react-ecosystem branch from f2c9fbd to 33b0dc5 Compare August 5, 2025 13:17
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 2 times, most recently from 331616a to db0ac5b Compare August 19, 2025 16:10
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 3 times, most recently from e71e3b0 to 1554285 Compare August 28, 2025 15:25
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 2 times, most recently from ada80e0 to 5eb164e Compare October 1, 2025 22:56
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 2 times, most recently from 2aab118 to ce58a77 Compare October 7, 2025 07:40
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 3 times, most recently from 3fd4b2a to 3ccf1fe Compare October 20, 2025 13:10
@renovate renovate bot force-pushed the renovate/react-ecosystem branch 4 times, most recently from 5f2a142 to f69d28b Compare November 6, 2025 15:49
@renovate renovate bot force-pushed the renovate/react-ecosystem branch from f69d28b to 4b20ada Compare November 12, 2025 05:45
@renovate renovate bot force-pushed the renovate/react-ecosystem branch from 4b20ada to 45a36a8 Compare November 20, 2025 13:06
@renovate renovate bot force-pushed the renovate/react-ecosystem branch from 45a36a8 to 53225d9 Compare December 3, 2025 16:31
@renovate renovate bot force-pushed the renovate/react-ecosystem branch from 53225d9 to 8b6f130 Compare December 11, 2025 21:41
@renovate renovate bot force-pushed the renovate/react-ecosystem branch from 8b6f130 to f6bc809 Compare December 12, 2025 05: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.

2 participants