Skip to content

Bump react from 19.2.5 to 19.2.6#494

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/react-19.2.6
Open

Bump react from 19.2.5 to 19.2.6#494
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/react-19.2.6

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 20, 2026

Bumps react from 19.2.5 to 19.2.6.

Release notes

Sourced from react's releases.

19.2.6 (May 6th, 2026)

React Server Components

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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

Low Risk
Low risk dependency-only update; behavior changes are limited to React internals and should surface primarily via build/runtime regressions if any.

Overview
Updates the React dependency from 19.2.5 to 19.2.6 in package.json and refreshes package-lock.json to the corresponding resolved artifact and integrity hash.

Reviewed by Cursor Bugbot for commit 3f60d44. Bugbot is set up for automated code reviews on this repo. Configure here.

Bumps [react](https://github.com/facebook/react/tree/HEAD/packages/react) from 19.2.5 to 19.2.6.
- [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.6/packages/react)

---
updated-dependencies:
- dependency-name: react
  dependency-version: 19.2.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added Changed Required label for PR that categorizes merge commit message as "Changed" for changelog dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels May 20, 2026
@socket-security
Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedreact@​19.2.5 ⏵ 19.2.61001008496100

View full report

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 3f60d44. Configure here.

Comment thread package.json
"clvm-lib": "^1.0.1",
"prism-react-renderer": "^2.4.1",
"react": "^19.2.5",
"react": "^19.2.6",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

react and react-dom version mismatch

High Severity

react is bumped to ^19.2.6 but react-dom remains at ^19.2.5. The lockfile resolves them to 19.2.6 and 19.2.5 respectively. These packages should always be the same version; a mismatch can cause runtime errors. react-dom should be bumped to ^19.2.6 as well.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 3f60d44. Configure here.

@github-actions
Copy link
Copy Markdown

🤖 Cursor Dependency Analysis

Supply-Chain Malware Review

Reviewing the dependency update and upstream changes for supply-chain risk.
Verdict: benign

Supply-chain review (concise)

Category Result
Classic obfuscation / eval / exfil / spawn No evidence. Scanner “shell_process_spawn” hits are false positives: RegExp.exec() on stack frames in ReactFlightReplyClient.js, not child_process. The “base64” hit is a literal error string in scripts/error-codes/codes.json, not encoded payload.
Invisible Unicode / GlassWorm Clear — scanner: 0 unicode, 0 confusable, 0 IOC.
Dependency integrity Normal patch 19.2.5 → 19.2.6; upstream range resolves to tagged commit eaf3e95 (“Version 19.2.6”) plus one functional commit 795203e ([FlightReply] type hardening). Lockfile entry is registry.npmjs.org/react/-/react-19.2.6.tgz with standard sha512- integrity. No ghost version or major skip.
Dependabot scope Expected manifest-only change: react in package.json / package-lock.json. No .github/workflows changes, no new install scripts, no new transitive packages flagged, no node_modules/ vendoring in the PR.

Upstream change (matches release notes)
The real diff is RSC Flight reply handling: prefix marker for nested FormData, new ReactFlightReplyBackingFormData.js, and Flow/type tightening in ReactFlightReplyServer.js — consistent with facebook/react#36425. This repo is a Docusaurus site; it does not run RSC servers, but the published react package still ships that code path upstream.

Scanner vs manual judgment
Status warn is from heuristic overmatch (exec, base64 in strings), not confirmed compromise. Manual review of the flagged lines agrees they are benign.

Non-security note (optional follow-up)
react is bumped to ^19.2.6 while react-dom remains ^19.2.5 in lockfile — version skew, not malware; aligning react-dom to 19.2.6 is good hygiene.

Recommendation: Approve from a supply-chain perspective. Run your usual CI (npm run build) before merge.

Compatibility Analysis

Analyzing React usage in the repo and upstream 19.2.6 changes for compatibility.

Compatibility & Adoption Analysis — react 19.2.5 → 19.2.6

1) Where react is used

Layer Usage
Direct dependency package.jsonreact@^19.2.6 (PR); react-dom still ^19.2.5
App components src/components/Runnable.tsx — hooks (useState, useEffect, useMemo), hydration guard; used heavily in MDX docs
src/components/Quiz.tsxuseReducer, useMemo (defined but not referenced in docs today)
src/utils/stringify.tsChildren, isValidElement, type utilities
MDX / Docusaurus Docs import <Runnable> from @site/src/components/Runnable.tsx; Docusaurus 3.10 + @mdx-js/react provide the React runtime for all pages
Transitive react-icons, react-simple-code-editor, prism-react-renderer, @docusaurus/*, @docsearch/react

Standard client-side React SPA/SSR site — no use server, no App Router, no direct RSC imports.


2) Intersection with changed upstream APIs

What actually changed in 19.2.6: one functional commit — [FlightReply] type hardening and performance (#36425) — touching:

  • packages/react-client/src/ReactFlightReplyClient.js
  • packages/react-server/src/ReactFlightReplyServer.js
  • New ReactFlightReplyBackingFormData.js

These are React Server Components Flight Reply internals (FormData serialization for server actions). Sibling packages (react-dom, react-server-dom-*, etc.) got version bumps only.

The react npm package itself has no source changes — only package.json version.

Overlap with this repo: none. Usage is limited to public client APIs (hooks, Children, JSX). Docusaurus does not ship or invoke RSC/Flight Reply code paths.


3) Risks / unknowns

Risk Severity Notes
RSC/Flight Reply behavior change Negligible Not used by Docusaurus or this codebase
react / react-dom version skew Low Lock resolves react@19.2.6, react-dom@19.2.5. Peer dep ^19.2.5 is satisfied. React publishes these as a set; aligning react-dom to 19.2.6 is good hygiene but not blocking
Public API / hook breakage Negligible No public API changes in react package
Build/runtime Low Patch bump; verify with npm run build
Malware scan heuristic hits on upstream None False positives (.exec() on regex stack-frame parsing in Flight Reply client)

4) Recommendation: merge

Safe to merge. This is a patch release whose only functional change is internal RSC Flight Reply plumbing that this Docusaurus docs site does not use. The react package artifact is effectively a version-only bump.

Optional follow-up (not a blocker): bump react-dom to ^19.2.6 in the same PR or a companion Dependabot PR to keep the React stack aligned.


Malware Scan Summary

  • Status: warn
  • Warn only mode: true
  • Changed upstream files scanned: 20
  • Resolution strategy: tag_range
  • Changed node/vendor paths: 0
  • Changed lockfiles: 0
  • Resolved upstream range: 23f4f9f30da9e9af2108c18bb197bae75ab584ea..eaf3e95ca92be7a23d3c9cc8ffd6f199a40be401
  • Resolved refs: from=23f4f9f30da9e9af2108c18bb197bae75ab584ea to=eaf3e95ca92be7a23d3c9cc8ffd6f199a40be401
  • Unicode findings (post-allowlist): 0
  • Confusable findings (post-allowlist): 0
  • IOC findings (post-allowlist): 0
  • Heuristic findings (post-allowlist): 3

Top findings

  • packages/react-client/src/ReactFlightReplyClient.js:1390 shell_process_spawn :: let parsed = v8FrameRegExp.exec(secondFrame);
  • packages/react-client/src/ReactFlightReplyClient.js:1392 shell_process_spawn :: parsed = jscSpiderMonkeyFrameRegExp.exec(secondFrame);
  • scripts/error-codes/codes.json:461 obfuscation_indicator :: "473": "React doesn't accept base64 encoded file uploads because we don't except form data passed from a browser to ever encode data that way. If that's the wrong assumption, we can easily fix it.",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Changed Required label for PR that categorizes merge commit message as "Changed" for changelog dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants