chore(deps): bump react and @types/react by dependabot[bot] · Pull Request #2588 · MetaMask/metamask-docs

dependabot · 2025-12-21T04:01:42Z

Bumps react and @types/react. These dependencies needed to be updated together.
Updates react from 18.3.1 to 19.2.3

Release notes

19.2.3 (December 11th, 2025)

React Server Components

Add extra loop protection to React Server Functions (@sebmarkbage #35351)

19.2.2 (December 11th, 2025)

React Server Components

Move react-server-dom-webpack/*.unbundled to private react-server-dom-unbundled (@eps1lon facebook/react#35290)

Patch Promise cycles and toString on Server Functions (@sebmarkbage, @unstubbable #35289, #35345)

19.2.1 (December 3rd, 2025)

React Server Components

Bring React Server Component fixes to Server Actions (@sebmarkbage #35277)

19.2.0 (Oct 1, 2025)

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:

resume: to resume a prerender to a stream.

resumeAndPrerender: to resume a prerender to HTML.

Added resume APIs for partial pre-rendering with Node Streams:

resumeToPipeableStream: to resume a prerender to a stream.

resumeAndPrerenderToNodeStream: to resume a prerender to HTML.

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

<Activity /> was developed over many years, starting before ClassComponent.setState (@acdlite @sebmarkbage and many others)

Stringify context as "SomeContext" instead of "SomeContext.Provider" (@kassens #33507)

Include stack of cause of React instrumentation errors with %o placeholder (@eps1lon #34198)

... (truncated)

Changelog

Sourced from react's changelog.

19.2.1 (Dec 3, 2025)

React Server Components

Bring React Server Component fixes to Server Actions (@sebmarkbage #35277)

19.2.0 (October 1st, 2025)

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:

resume: to resume a prerender to a stream.

resumeAndPrerender: to resume a prerender to HTML.

Added resume APIs for partial pre-rendering with Node Streams:

resumeToPipeableStream: to resume a prerender to a stream.

resumeAndPrerenderToNodeStream: to resume a prerender to HTML.

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

<Activity /> was developed over many years, starting before ClassComponent.setState (@acdlite @sebmarkbage and many others)

Stringify context as "SomeContext" instead of "SomeContext.Provider" (@kassens #33507)

Include stack of cause of React instrumentation errors with %o placeholder (@eps1lon #34198)

Fix infinite useDeferredValue loop in popstate event (@acdlite #32821)

Fix a bug when an initial value was passed to useDeferredValue (@acdlite #34376)

Fix a crash when submitting forms with Client Actions (@sebmarkbage #33055)

Hide/unhide the content of dehydrated suspense boundaries if they resuspend (@sebmarkbage #32900)

Avoid stack overflow on wide trees during Hot Reload (@sophiebits #34145)

Improve Owner and Component stacks in various places (@sebmarkbage, @eps1lon: #33629, #33724, #32735, #33723)

Add cacheSignal (@sebmarkbage #33557)

... (truncated)

Commits

612e371 Version 19.2.3
b910fc1 Version 19.2.2
053df4e Version 19.2.1
5667a41 Bump next prerelease version numbers (#34639)
8bb7241 Bump useEffectEvent to Canary (#34610)
e3c9656 Ensure Performance Track are Clamped and Don't overlap (#34509)
68f00c9 Release Activity in Canary (#34374)
0e10ee9 [Reconciler] Set ProfileMode for Host Root Fiber by default in dev (#34432)
3bf8ab4 Add missing Activity export to development mode (#34439)
1549bda [Flight] Only assign _store in dev mode when creating lazy types (#34354)
Additional commits viewable in compare view

Updates @types/react from 18.3.9 to 19.2.7

Commits

See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note

Updates dependency versions only.

Bumps react to ^19.2.3 in package.json
Bumps @types/react to ^19.2.8 in package.json

^{Written by Cursor Bugbot for commit bba209a. This will update automatically on new commits. Configure here.}

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

dependabot · 2025-12-21T04:01:43Z

Assignees

The following users could not be added as assignees: protocol-galileo. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

vercel · 2025-12-21T04:01:45Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
metamask-docs	Error		Jan 18, 2026 4:14am

socket-security · 2025-12-21T04:02:21Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@types/react@19.1.15 ⏵ 19.2.8			⁺¹	^-3
	react@19.2.3

View full report

socket-security · 2025-12-21T04:02:23Z

Caution

MetaMask internal reviewing guidelines:

Do not ignore-all
Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
@SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert (click "▶" to expand/collapse)
Block		Network access: npm `caniuse-lite` in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: package-lock.json → `npm/node-polyfill-webpack-plugin@2.0.1` → `npm/@metamask/profile-sync-controller@16.0.0` → `npm/docusaurus-plugin-sass@0.2.5` → `npm/react-spring@10.0.3` → `npm/@docusaurus/theme-mermaid@3.9.2` → `npm/@docusaurus/plugin-client-redirects@3.9.2` → `npm/@docusaurus/plugin-google-tag-manager@3.9.2` → `npm/@docusaurus/types@3.9.2` → `npm/@docusaurus/preset-classic@3.9.2` → `npm/@docusaurus/plugin-content-pages@3.9.2` → `npm/@docusaurus/theme-common@3.9.2` → `npm/@docusaurus/plugin-google-gtag@3.9.2` → `npm/@docusaurus/plugin-content-docs@3.9.2` → `npm/@docusaurus/core@3.9.2` → `npm/caniuse-lite@1.0.30001764` ℹ Read more on: This package \| This alert \| What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001764`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Publisher changed: npm `@docsearch/core` is now published by dylantientcheu instead of shortcuts New Author: dylantientcheu Previous Author: shortcuts From: package-lock.json → `npm/@docusaurus/preset-classic@3.9.2` → `npm/@docsearch/core@4.4.0` ℹ Read more on: This package \| This alert \| What is new author? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@docsearch/core@4.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Publisher changed: npm `@docsearch/css` is now published by dylantientcheu instead of shortcuts New Author: dylantientcheu Previous Author: shortcuts From: package-lock.json → `npm/@docusaurus/preset-classic@3.9.2` → `npm/@docsearch/css@4.4.0` ℹ Read more on: This package \| This alert \| What is new author? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@docsearch/css@4.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Publisher changed: npm `@docsearch/react` is now published by dylantientcheu instead of shortcuts New Author: dylantientcheu Previous Author: shortcuts From: package-lock.json → `npm/@docusaurus/preset-classic@3.9.2` → `npm/@docsearch/react@4.4.0` ℹ Read more on: This package \| This alert \| What is new author? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@docsearch/react@4.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Publisher changed: npm `finalhandler` is now published by ulisesgascon instead of wesleytodd New Author: ulisesgascon Previous Author: wesleytodd From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/finalhandler@1.3.2` ℹ Read more on: This package \| This alert \| What is new author? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/finalhandler@1.3.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Publisher changed: npm `http-errors` is now published by ulisesgascon instead of dougwilson New Author: ulisesgascon Previous Author: dougwilson From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/http-errors@2.0.1` ℹ Read more on: This package \| This alert \| What is new author? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/http-errors@2.0.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Publisher changed: npm `statuses` is now published by ulisesgascon instead of dougwilson New Author: ulisesgascon Previous Author: dougwilson From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/statuses@2.0.2` ℹ Read more on: This package \| This alert \| What is new author? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/statuses@2.0.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `core-js-pure` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code is a standard, non-malicious implementation of multiple Array prototype iteration methods from core-js. It reads input from the provided array-like object and a user-provided callback, and writes results into a created target array where appropriate. There is no evident data exfiltration, backdoor, or other malicious activity. Overall security risk appears low to moderate in isolation, with no suspicious behavior detected in this fragment. Confidence: 1.00 Severity: 0.60 From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/core-js-pure@3.47.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/core-js-pure@3.47.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `core-js` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code is a standard, non-malicious implementation of multiple Array prototype iteration methods from core-js. It reads input from the provided array-like object and a user-provided callback, and writes results into a created target array where appropriate. There is no evident data exfiltration, backdoor, or other malicious activity. Overall security risk appears low to moderate in isolation, with no suspicious behavior detected in this fragment. Confidence: 1.00 Severity: 0.60 From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/core-js@3.47.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/core-js@3.47.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `core-js` is 100.0% likely to have a medium risk anomaly Notes: The code constitutes a standards-compliant polyfill/compatibility patch for RegExp/String.prototype.replace with robust handling of named groups and replacer semantics. No evidence of malware, exfiltration, or sensitive data leakage. The risk profile is typical for polyfills in open-source libraries and is acceptable when used in trusted contexts, albeit with standard caution about using third-party dependencies in supply chains. Confidence: 1.00 Severity: 0.60 From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/core-js@3.47.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/core-js@3.47.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `core-js` is 100.0% likely to have a medium risk anomaly Notes: The code implements a targeted safety polyfill for Uint8Array.prototype.setFromBase64 to support base64 decoding into typed arrays. It includes environment feature checks and uses internal decoding helpers to fill the array and report read/written counts. No malicious activity detected; the flow is confined to in-memory decoding and prototype augmentation. This appears to be a legitimate compatibility helper rather than malware. Confidence: 1.00 Severity: 0.60 From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/core-js@3.47.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/core-js@3.47.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `core-js` is 100.0% likely to have a medium risk anomaly Notes: The fragment implements a conventional abstract AsyncIterator polyfill pattern. It prevents direct construction, attaches type metadata, and exposes AsyncIteratorConstructor globally in a controlled manner. There are no signs of data exfiltration, external I/O, or hidden behavior. Overall security risk is low, malware likelihood is negligible in this fragment, and the code aligns with legitimate library usage (e.g., core-js style shims). Confidence: 1.00 Severity: 0.60 From: package-lock.json → `npm/@docusaurus/core@3.9.2` → `npm/core-js@3.47.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/core-js@3.47.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

cursor · 2026-01-11T04:30:26Z

package.json

    "prettier": "^3.6.2",
    "prism-react-renderer": "^2.4.1",
-    "react": "^18.0.0",
+    "react": "^19.2.3",


React 19 and React DOM 18 version mismatch

High Severity

The react package was updated to version ^19.2.3 but react-dom remains at ^18.0.0. React and React DOM must use the same major version to be compatible. This version mismatch will cause runtime errors because React 19's internal APIs are incompatible with React DOM 18. The react-dom dependency needs to be updated to version 19.x alongside the react update.

cursor · 2026-01-11T04:30:26Z

package.json

    "prettier": "^3.6.2",
    "prism-react-renderer": "^2.4.1",
-    "react": "^18.0.0",
+    "react": "^19.2.3",


Override forces React 18 conflicting with React 19

Medium Severity

The overrides section forces react-alert to use react: ^18.0.0 and react-dom: ^18.0.0, which was compatible when the main project used React 18. With react now upgraded to ^19.2.3, this override creates a version conflict that can cause npm to install both React 18 and React 19. Having multiple React versions at runtime causes the well-known "Invalid Hook Call" error and breaks component state sharing between packages.

Bumps [react](https://github.com/facebook/react/tree/HEAD/packages/react) and [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react). These dependencies needed to be updated together. Updates `react` from 18.3.1 to 19.2.3 - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.3/packages/react) Updates `@types/react` from 18.3.9 to 19.2.7 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react) --- updated-dependencies: - dependency-name: react dependency-version: 19.2.3 dependency-type: direct:production update-type: version-update:semver-major - dependency-name: "@types/react" dependency-version: 19.2.7 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2026-01-28T08:12:53Z

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Dec 21, 2025

dependabot bot requested review from a team as code owners December 21, 2025 04:01

vercel bot had a problem deploying to Preview December 21, 2025 04:02 Failure

dependabot bot force-pushed the dependabot/npm_and_yarn/multi-e1aa4930cf branch from 17d65ef to 102a2a1 Compare January 11, 2026 04:27

vercel bot had a problem deploying to Preview January 11, 2026 04:27 Failure

cursor bot reviewed Jan 11, 2026

View reviewed changes

dependabot bot force-pushed the dependabot/npm_and_yarn/multi-e1aa4930cf branch from 102a2a1 to bba209a Compare January 18, 2026 04:13

vercel bot had a problem deploying to Preview January 18, 2026 04:14 Failure

shahbaz17 closed this Jan 28, 2026

dependabot bot deleted the dependabot/npm_and_yarn/multi-e1aa4930cf branch January 28, 2026 08:12

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): bump react and @types/react#2588

chore(deps): bump react and @types/react#2588
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/multi-e1aa4930cf

dependabot bot commented on behalf of github Dec 21, 2025 •

edited

Loading

Uh oh!

dependabot bot commented on behalf of github Dec 21, 2025

Uh oh!

vercel bot commented Dec 21, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Dec 21, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Dec 21, 2025 •

edited

Loading

Uh oh!

cursor bot Jan 11, 2026

Uh oh!

cursor bot Jan 11, 2026

Uh oh!

dependabot bot commented on behalf of github Jan 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

dependabot bot commented on behalf of github Dec 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

19.2.3 (December 11th, 2025)

React Server Components

19.2.2 (December 11th, 2025)

React Server Components

19.2.1 (December 3rd, 2025)

React Server Components

19.2.0 (Oct 1, 2025)

New React Features

New React DOM Features

Notable changes

All Changes

React

19.2.1 (Dec 3, 2025)

React Server Components

19.2.0 (October 1st, 2025)

New React Features

New React DOM Features

Notable changes

All Changes

React

Uh oh!

dependabot bot commented on behalf of github Dec 21, 2025

Assignees

Uh oh!

vercel bot commented Dec 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Dec 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Dec 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cursor bot Jan 11, 2026

Choose a reason for hiding this comment

React 19 and React DOM 18 version mismatch

Uh oh!

cursor bot Jan 11, 2026

Choose a reason for hiding this comment

Override forces React 18 conflicting with React 19

Uh oh!

dependabot bot commented on behalf of github Jan 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dependabot bot commented on behalf of github Dec 21, 2025 •

edited

Loading

vercel bot commented Dec 21, 2025 •

edited

Loading

socket-security bot commented Dec 21, 2025 •

edited

Loading

socket-security bot commented Dec 21, 2025 •

edited

Loading