Skip to content

Bump react-dom from 18.3.1 to 19.2.0 - #1

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

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

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 21, 2025 •

Copy link
Copy Markdown
Contributor

Bumps react-dom from 18.3.1 to 19.2.0.

Release notes

Sourced from react-dom's releases.

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

... (truncated)

Changelog

Sourced from react-dom's changelog.

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

React DOM

... (truncated)

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

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 21, 2025
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch 6 times, most recently from 6434ff2 to 8883acf Compare October 25, 2025 21:31
@vercel

vercel Bot commented Oct 25, 2025 •

Copy link
Copy Markdown

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

Project Deployment Preview Comments Updated (UTC)
superset-website Error Error Oct 28, 2025 0:00am

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch from 8883acf to 265b8fc Compare October 27, 2025 03:23
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch from 265b8fc to b10d6b6 Compare October 27, 2025 03:39
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch from b10d6b6 to 331f1d7 Compare October 27, 2025 03:41
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch from 331f1d7 to 82ea50b Compare October 27, 2025 20:30
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch from 82ea50b to cbd6f25 Compare October 27, 2025 20:53
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch from cbd6f25 to 89925be Compare October 27, 2025 22:41
Bumps [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) from 18.3.1 to 19.2.0.
- [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.0/packages/react-dom)

---
updated-dependencies:
- dependency-name: react-dom
  dependency-version: 19.2.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/react-dom-19.2.0 branch from 89925be to c4ddf19 Compare October 27, 2025 23:59
@dependabot @github

dependabot Bot commented on behalf of github Oct 28, 2025

Copy link
Copy Markdown
Contributor Author

Looks like react-dom is no longer updatable, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 28, 2025
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/react-dom-19.2.0 branch October 28, 2025 04:16
AlexGodard added a commit to AlexGodard/superset that referenced this pull request Jul 20, 2026
…t session (ParadevAI#1)

New 'superset agents send <sessionId> <text...> --workspace <id>' command
calls the existing terminal.writeInput mutation, appending LF iff absent
(mirrors normalizeTerminalCommand) so the message renders live in the
desktop session. No backend changes.
caiokf added a commit to caiokf/superset that referenced this pull request Aug 12, 2026
A file dropped on a v1 terminal pane was written straight to the PTY, so
the foreground app saw it as typing. Agent TUIs use the bracketed-paste
envelope to tell a dropped path apart from a typed one, so the path was
left as literal text and the image was never attached (ParadevAI#6370).

Measured against Claude Code 2.1.215 in a real PTY (tmux, 120x45, path
`/tmp/drop-probe/scratch/My Screenshot.png`, file present on disk):

  single-quoted  + bracketed paste  -> [Image ParadevAI#1]
  backslash-esc. + bracketed paste  -> [Image ParadevAI#1]
  single-quoted  + typed            -> literal text
  backslash-esc. + typed            -> literal text

The delivery is what decides it; the escaping style makes no difference.
v2 panes already call xterm's paste(), and so does Cmd+V in a v1 pane —
route the drop through the same call.
saddlepaddle added a commit that referenced this pull request Sep 6, 2026
… route to the diff

Every navigation to files-changed comes from PullRequestScreen, so without a
pull request the diff is unreachable — and "review the diff from your phone" is
what the store listing promises. It had been unreachable since this box was
rebuilt.

The cause was setup.sh creating the demo repos with `git init`. The original
/demo/acme was a clone of the public superset-sh/acme-demo, whose open PR #1
matches the fix-input-overflow workspace. A fresh init produced unrelated
history, no origin, and no refs/remotes/origin/HEAD — which also silently broke
the diff base, since getDefaultBranchName reads exactly that ref. setup.sh now
clones, so the PR and the diff base both come back on their own rather than from
refs fabricated to paper over the init.

The host also needs a token: ctx.github() throws NO_GITHUB_TOKEN rather than
falling back to unauthenticated, even on a public repo. A fine-grained
public-repositories read-only PAT lives in /etc/superset-review-host.env (0600,
root), read through EnvironmentFile=- so it stays out of world-readable unit
files, out of `gh auth login`, and out of the worktrees.

That PAT expires 2026-10-05, and an expired one removes the headline feature
without any other symptom, so check.sh calls the GitHub API with it every run and
fails loudly. The README carries the rotation command.

Verified on device: home shows diff stats per row, the chip renders in the
quick-key bar, and it opens PR #1 through to a syntax-highlighted two-file diff.

Claude-Session: https://claude.ai/code/session_0126YNrKGh5P6h9a2S9j1YAj
saddlepaddle added a commit that referenced this pull request Sep 6, 2026
… on expired credentials (#7216)

* fix(review-host): give the reviewer a diff to review, and stop paging on expired credentials

Two things found driving the app as the reviewer sees it.

The store listing promises "review the diff from your phone" and every demo
workspace had an empty diff. Two separate causes. The worktrees were rebuilt as
bare branches during the GCP move, so there was nothing committed on them; each
now carries one small change matching its name. And the demo repos are created
by `git init`, so they have no refs/remotes/origin/HEAD — getDefaultBranchName
reads exactly that ref, returns null, resolveBaseComparison gives up, and
listCommits returns [] no matter what is on the branch. They were clones before
this box was rebuilt, which is why nobody had seen it. setup.sh now fabricates
origin/main and origin/HEAD locally; there is no remote to fetch and nothing
tries, so the base resolves offline.

check.sh asserts every demo workspace has a diff, because an empty one is a
listing mismatch rather than a cosmetic gap, and it has now been empty twice for
different reasons.

check.sh also exits 2 with INCONCLUSIVE when gcloud cannot authenticate, instead
of reporting the instance as missing. Every probe runs through gcloud, so an
expired refresh token made a healthy box look down — and the automation pages
someone for a down box. It found this the honest way: the token expired
mid-session.

Claude-Session: https://claude.ai/code/session_0126YNrKGh5P6h9a2S9j1YAj

* feat(review-host): restore the pull-request chip, the reviewer's only route to the diff

Every navigation to files-changed comes from PullRequestScreen, so without a
pull request the diff is unreachable — and "review the diff from your phone" is
what the store listing promises. It had been unreachable since this box was
rebuilt.

The cause was setup.sh creating the demo repos with `git init`. The original
/demo/acme was a clone of the public superset-sh/acme-demo, whose open PR #1
matches the fix-input-overflow workspace. A fresh init produced unrelated
history, no origin, and no refs/remotes/origin/HEAD — which also silently broke
the diff base, since getDefaultBranchName reads exactly that ref. setup.sh now
clones, so the PR and the diff base both come back on their own rather than from
refs fabricated to paper over the init.

The host also needs a token: ctx.github() throws NO_GITHUB_TOKEN rather than
falling back to unauthenticated, even on a public repo. A fine-grained
public-repositories read-only PAT lives in /etc/superset-review-host.env (0600,
root), read through EnvironmentFile=- so it stays out of world-readable unit
files, out of `gh auth login`, and out of the worktrees.

That PAT expires 2026-10-05, and an expired one removes the headline feature
without any other symptom, so check.sh calls the GitHub API with it every run and
fails loudly. The README carries the rotation command.

Verified on device: home shows diff stats per row, the chip renders in the
quick-key bar, and it opens PR #1 through to a syntax-highlighted two-file diff.

Claude-Session: https://claude.ai/code/session_0126YNrKGh5P6h9a2S9j1YAj

* feat(review-host): give acme-ios a pull request too, and clone both demo repos

The pull-request chip is the only navigation to files-changed, so a project
without a PR has no route to the diff at all — and diff review is what the store
listing promises. acme had one through superset-sh/acme-demo; acme-ios had no
GitHub repository, so half the reviewer's projects were a dead end.

Adds superset-sh/acme-ios-demo (public, same shape as acme-demo: a composer, a
test, and an open PR adding haptics) and clones it alongside acme. Both demo
projects now carry one PR-linked workspace and two with a diff but no PR, which
is what a real project looks like.

Cloning also retires the workaround underneath. setup.sh used to `git init` the
demo repos and then fabricate refs/remotes/origin/main and origin/HEAD so the
diff base could resolve; a clone brings both refs, the branches, and the PR
without inventing anything. The vendored demo/ copy and its biome exclusion go
with it — it had already drifted from the real repositories, which is how the
two got out of step.

check.sh now asserts at least one workspace has a linked pull request. Every
other check can pass while the chip is gone, and the chip is the whole path to
the feature the listing sells.

Verified end to end on device for both projects, and setup.sh re-run to confirm
it stays idempotent against existing clones.

Claude-Session: https://claude.ai/code/session_0126YNrKGh5P6h9a2S9j1YAj

* fix(review-host): re-clone a legacy demo repo, and keep ids and tokens off the remote command line

Three from the bot reviews on this branch, all real.

setup.sh guarded the demo clone on `.git` existing, so a host provisioned by the
earlier version — where the repos were `git init`ed and their refs fabricated —
would keep those forever: no origin, no PR, no diff base, which is the exact
state this branch replaced. The guard is now the origin URL, so a legacy repo is
re-cloned and a correct one is only fetched.

check.sh interpolated workspace ids into commands a remote shell parses.
workspace.adopt takes an unrestricted existingWorkspaceId, so the host database
is not a trusted source of shell-safe strings. Ids that are not plain uuids are
dropped — and because dropping one silently would hide a workspace from every
probe below, which is the fail-open shape this script keeps getting wrong,
dropping any is itself a failure.

The README's rotation command passed the PAT as an argument, which lands in
local shell history and in ps output and auth logs on the box. It goes over
stdin now.

Also asserts both demo projects have a linked pull request rather than at least
one: with a PR per project, one link surviving means the other project has no
route to a diff at all, and check.sh was reporting that as fine. The token probe
covers both repositories for the same reason.

Verified on the live box: setup.sh re-run leaves both clones with the right
origin and origin/HEAD, and check.sh passes all twelve assertions.

Claude-Session: https://claude.ai/code/session_0126YNrKGh5P6h9a2S9j1YAj
harshithmullapudi added a commit that referenced this pull request Nov 14, 2026
…ore recording it ready

- MoveBook stores the attempt that claimed a copy. Only that attempt can
  claim it again (a lost answer), finish it, or fail it (`failAttempt`).
  Another attempt takes over only once the copy has been quiet longer than
  any step (CLAIM_LEASE_MS, 3 min). The column is added to existing books.
- The cloud job and the desktop name their attempt. A job whose claim call
  throws now fails only its own copy, so a lost claim answer no longer
  leaves the move copying (#4), and it can no longer fail a copy a
  duplicate job is running. Two windows can no longer run one move (#7).
- completeChatMove marks the move `switching` (restoring) inside the
  Postgres transaction, commits the chat's new workspace, and records the
  move ready only after (#1). `failChatMove` checks Postgres first and
  records a chat that did switch as done. `chatMove.latest` reconciles a
  move the sweep failed after its chat switched.
- Released desktops (no attemptId) keep the reclaim-by-owner path. Against
  a realtime that does not know the new ops yet, the API falls back to the
  old order.
harshithmullapudi added a commit that referenced this pull request Nov 14, 2026
…tch before ready (#9729)

* fix(shared): tighten workspace move transitions in the MoveBook

- abandon now ends a move that already has its destination: its chats
  still in flight fail and the move settles. Before, it returned ok and
  changed nothing, so a move whose destination the desktop had just
  destroyed stayed "moving" until the 6-minute sweep.
- begin refuses while chats or a workspace move are still arriving in the
  workspace, so a chat cannot land after the workspace's snapshot was
  taken and be left behind.
- retry refuses a move with no destination yet, and a move the workspace
  has since moved again after, so an old attempt cannot reopen a finished
  move and send a chat to an old destination.

* fix(trpc): stop a lost claim or one failed publish from stranding chat moves

- runChatMove: when claim throws (its answer lost after it landed), fail
  the move before rethrowing. The QStash redelivery would otherwise find
  nothing pending, skip, and leave the move copying until the stale sweep.
- workspaceMove.attach: a move that cannot start now fails on its own and
  the loop goes on, instead of throwing and leaving the later chats
  pending with nothing to queue them.
- Integration test for the lost claim; end the move a test left arriving
  in MY_CLOUD, which the new begin check would otherwise trip over.

* fix(desktop,host-service): move open chats past closed ones, release chats when a move ends mid-prepare

- prepareWorkspace cut the chat list at 50 before skipping closed chats,
  so an open chat behind 50 closed ones was silently left behind. Skip
  closed chats first, and report open chats beyond 50 as "too_many".
- When the move ended while prepareWorkspace was still running, the catch
  had already released the empty lists and the late branch released only
  terminals, so the source kept following the chats. Release both there,
  and clear the record so the catch never releases them twice.

* fix: keep terminals that failed to restart for a retry; drop the lost-claim fix

- When a move ends mid-prepare, keep the terminal ids releaseSourceTerminals
  could not restart in leaving.terminals, so the outer catch tries them
  again, as it did before the previous commit cleared the list.
- Revert failing a chat move when its claim call throws. The catch cannot
  tell a claim that landed with its answer lost from a duplicate job whose
  claim never landed while another job copies the move, so it could fail a
  healthy move mid-import. It needs a per-attempt claim token in the
  MoveBook, which goes with the claim-token follow-up.

* fix: give each chat-move run its own attempt, and switch the chat before recording it ready

- MoveBook stores the attempt that claimed a copy. Only that attempt can
  claim it again (a lost answer), finish it, or fail it (`failAttempt`).
  Another attempt takes over only once the copy has been quiet longer than
  any step (CLAIM_LEASE_MS, 3 min). The column is added to existing books.
- The cloud job and the desktop name their attempt. A job whose claim call
  throws now fails only its own copy, so a lost claim answer no longer
  leaves the move copying (#4), and it can no longer fail a copy a
  duplicate job is running. Two windows can no longer run one move (#7).
- completeChatMove marks the move `switching` (restoring) inside the
  Postgres transaction, commits the chat's new workspace, and records the
  move ready only after (#1). `failChatMove` checks Postgres first and
  records a chat that did switch as done. `chatMove.latest` reconciles a
  move the sweep failed after its chat switched.
- Released desktops (no attemptId) keep the reclaim-by-owner path. Against
  a realtime that does not know the new ops yet, the API falls back to the
  old order.

* feat(host-service): undo what a move stopped on the source, without the desktop that ran it

When the desktop that runs a move quits, reloads, or loses the reply to
prepareWorkspace, the terminals it stopped stayed stopped: only the
renderer ever started them again (#2).

- prepareWorkspace takes an optional workspaceMoveId. With it, the host
  records the terminals it stopped and the chats it follows in a new
  workspace_move_undos table (migration 0039).
- handOffTerminals marks each terminal handing off on the source
  (teleport.markHandingOff) before importing it at the destination. If the
  source cannot record that, the terminal is held back, so the host never
  starts again a terminal that did move. A source too old to know the call
  keeps no record, so the handoff goes on.
- Every minute and at boot the host reads each recorded move through the
  new workspaceMove.status query, which does not keep a move alive. Once
  the move is over (at once if it never got a destination, else after a
  15-minute handoff window) it starts the terminals not handed off and
  forgets the chats. A move whose status cannot be read is left alone.
- releaseTerminals and releaseChats drop what the desktop already put
  back, so nothing is put back twice.

Desktops that do not pass workspaceMoveId keep today's behaviour.

* Revert "feat(host-service): undo what a move stopped on the source, without the desktop that ran it"

This reverts commit 24e35de.

* fix: address review of the move attempts and abandon rules

- finish and switching accept a copy claimed without an attempt, and a
  caller holding a copy can fail one (failAttempt orUnowned). A copy an
  older realtime or API claimed during a deploy no longer hangs until the
  sweep when a newer one completes it. The claim-throw path stays strict.
- The desktop's resume after a reload retries a move another run still
  holds each minute, for six rounds, so it takes the copy over once the
  claim lease runs out, before the sweep fails it. runMoveOnComputer now
  says when another run holds the copy.
- The cloud job touches its copy between waking the box, building the
  import and importing, and CLAIM_LEASE_MS is 4 min, so a redelivery
  cannot take over a job that is still working.
- abandon ends a move that has a destination only when asked
  (withDestination, sent by the desktop whose move could not finish, never
  by the banner's cancel), never fails a chat that is switching, and
  returns the chats that moved. The desktop releases only the others.
- retry refuses only when this chat moved again in a later move, so a later
  move cancelled before it got a destination no longer blocks it.
- attach lists a chat whose move could not start in skipped.
- The integration tests end moves into MY_CLOUD in afterEach, so a failed
  assertion cannot cascade, and cover a copy claimed by an older store.

---------

Co-authored-by: Harshith Mullapudi <17528887+harshithmullapudi@users.noreply.github.com>

This branch had an error being deployed

1 failed deployment
Preview — c4ddf19f Deployed Oct 28, 2025 by vercel[bot]
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.

0 participants