Skip to content

chore(deps): bump react-dom from 19.1.0 to 19.2.7 - #78

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/react-dom-19.2.7
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/react-dom-19.2.7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 19, 2026

Copy link
Copy Markdown
Contributor

Bumps react-dom from 19.1.0 to 19.2.7.

Release notes

Sourced from react-dom's releases.

19.2.7 (June 1st, 2026)

React Server Components

19.2.6 (May 6th, 2026)

React Server Components

19.2.5 (April 8th, 2026)

React Server Components

19.2.4 (January 26th, 2026)

React Server Components

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)

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

... (truncated)

Changelog

Sourced from react-dom's changelog.

19.2.1 (Dec 3, 2025)

React Server Components

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:
  • 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

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-dom since your current version.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 19, 2026
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 19, 2026

Copy link
Copy Markdown

Deploying agent-render with  Cloudflare Pages  Cloudflare Pages

Latest commit: eb5c6f5
Status:🚫  Build failed.

View logs

@socket-security

socket-security Bot commented Jun 19, 2026

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-dom@​19.1.0 ⏵ 19.2.7100 +110092 +198100

View full report

@greptile-apps

greptile-apps Bot commented Jun 19, 2026

Copy link
Copy Markdown

Greptile Summary

This is an automated dependabot PR that bumps react-dom from 19.1.0 to 19.2.7, picking up Server Action fixes, DoS hardening for React Server Functions, and the new React 19.2 features (<Activity>, useEffectEvent, partial pre-rendering resume APIs). The package-lock.json is regenerated accordingly, with scheduler moving from 0.26.0 to 0.27.0 as a transitive update.

  • react-dom bumped to 19.2.7; scheduler transitively bumped to 0.27.0.
  • Many "peer": true metadata flags reshuffled in package-lock.json — this is normal npm behaviour when the dependency tree is reresolved.
  • react stays at 19.1.0 while react-dom@19.2.7 declares "react": "^19.2.7" as its peer dependency, which is a mismatch that was already flagged in a prior review comment.

Confidence Score: 4/5

The lockfile changes look mechanically correct, but react and react-dom are now on different minor versions with an unsatisfied peer dependency constraint that was called out in a prior review.

The react-dom bump itself is straightforward and the lockfile regeneration is normal. The unresolved peer dependency conflict between react@19.1.0 and react-dom@19.2.7 (which requires ^19.2.7) means npm installs may warn or fail in strict environments, and running mismatched minor versions of react and react-dom is not a supported configuration.

package.json — react needs to be co-bumped to 19.2.7 to satisfy react-dom's peer dependency constraint

Important Files Changed

Filename Overview
package.json Bumps react-dom from 19.1.0 to 19.2.7; react remains at 19.1.0 while react-dom@19.2.7 declares peerDependency "react": "^19.2.7"
package-lock.json Lockfile regenerated by npm; react-dom updated to 19.2.7, scheduler bumped to 0.27.0, and numerous peer/dev metadata flags reshuffled as expected after a dependency tree change

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["package.json<br/>react: 19.1.0 (unchanged)"]
    B["package.json<br/>react-dom: 19.2.7 (bumped)"]
    C["package-lock.json<br/>react-dom@19.2.7<br/>peerDep: react ^19.2.7"]
    D["package-lock.json<br/>scheduler@0.27.0 (bumped)"]
    E{{"⚠ Peer dep mismatch<br/>19.1.0 does not satisfy ^19.2.7"}}

    B --> C
    C --> D
    A -->|satisfies?| E
    C -->|requires| E
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["package.json<br/>react: 19.1.0 (unchanged)"]
    B["package.json<br/>react-dom: 19.2.7 (bumped)"]
    C["package-lock.json<br/>react-dom@19.2.7<br/>peerDep: react ^19.2.7"]
    D["package-lock.json<br/>scheduler@0.27.0 (bumped)"]
    E{{"⚠ Peer dep mismatch<br/>19.1.0 does not satisfy ^19.2.7"}}

    B --> C
    C --> D
    A -->|satisfies?| E
    C -->|requires| E
Loading

Reviews (2): Last reviewed commit: "chore(deps): bump react-dom from 19.1.0 ..." | Re-trigger Greptile

Comment thread package.json Outdated
@@ -69,7 +69,7 @@
"next-themes": "^0.4.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.

P1 React/react-dom version mismatch

react-dom@19.2.7 declares "react": "^19.2.7" as its peer dependency (visible in package-lock.json), but react remains pinned to 19.1.0. 19.1.0 does not satisfy ^19.2.7 (>=19.2.7 <20.0.0). npm 7+ treats unsatisfied peer deps as install errors, so npm install or CI dependency installs may fail, and even if they don't, running mismatched react + react-dom minor versions can trigger subtle reconciler bugs or runtime warnings. react should be bumped to 19.2.7 in the same PR.

Fix in Codex

@kilo-code-bot

kilo-code-bot Bot commented Jun 19, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

This Dependabot PR bumps react-dom from 19.1.0 to 19.2.7 (and the transitive scheduler dependency from 0.26.0 to 0.27.0). The bump itself is valid, but it leaves react pinned at 19.1.0, which no longer satisfies react-dom@19.2.7's peer dependency (react: ^19.2.7). This will cause npm install / npm ci to fail with an ERESOLVE peer-dependency error, and running mismatched react / react-dom minor versions risks subtle reconciler bugs and runtime warnings.

Overview

Severity Count
CRITICAL 1
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
package.json 68 react pinned at 19.1.0 (line 67) while react-dom@19.2.7 requires react: ^19.2.7 (peer dependency). Bump react to 19.2.7 in this same PR.

ℹ️ This issue is already flagged by an existing review comment (Greptile) anchored at package.json:69, so no duplicate inline comment was posted here.

Files Reviewed (2 files)
  • package.json — 1 issue (react/react-dom version mismatch; already flagged by an existing review comment)
  • package-lock.json — 0 issues (scheduler bump from 0.26.00.27.0 is the expected transitive dependency of react-dom@19.2.7; remaining changes are lock-file peer-flag churn)

Fix these issues in Kilo Cloud

Previous Review Summary (commit 0ee63b6)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 0ee63b6)

Status: 1 Issue Found | Recommendation: Address before merge

This Dependabot PR bumps react-dom from 19.1.0 to 19.2.7 (and the transitive scheduler dependency from 0.26.0 to 0.27.0). The bump itself is valid, but it leaves react pinned at 19.1.0, which no longer satisfies react-dom@19.2.7's peer dependency (react: ^19.2.7). This will cause npm install / npm ci to fail with an ERESOLVE peer-dependency error, and running mismatched react / react-dom minor versions risks subtle reconciler bugs and runtime warnings.

Overview

Severity Count
CRITICAL 1
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
package.json 71 react pinned at 19.1.0 while react-dom@19.2.7 requires react: ^19.2.7 (peer dependency). Bump react to 19.2.7 in this same PR.

ℹ️ This issue is already flagged by an existing review comment (Greptile) anchored at package.json:69, so no duplicate inline comment was posted here.

Files Reviewed (2 files)
  • package.json — 1 issue (react/react-dom version mismatch; already flagged by an existing review comment)
  • package-lock.json — 0 issues (scheduler bump from 0.26.00.27.0 is the expected transitive dependency of react-dom@19.2.7)

Fix these issues in Kilo Cloud


Reviewed by GLM-5.2 · Input: 55.5K · Output: 5.7K · Cached: 208.3K

Bumps [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) from 19.1.0 to 19.2.7.
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v19.2.7/packages/react-dom)

---
updated-dependencies:
- dependency-name: react-dom
  dependency-version: 19.2.7
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@baanish

baanish commented Jun 19, 2026

Copy link
Copy Markdown
Owner

Superseded by #79, which bumps this dependency (and the rest of the safe batch) together and is merged into main. react/react-dom were bumped in lockstep there to satisfy the peer constraint that broke #78 alone.

@baanish baanish closed this Jun 19, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jun 19, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. 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
dependabot Bot deleted the dependabot/npm_and_yarn/react-dom-19.2.7 branch June 19, 2026 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

1 participant