chore(deps): bump react-dom and @types/react-dom in /client - #179
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Owner
|
Blocked — CI red (build, test, smoke): cannot be merged alone. Other half of #175: Generated by Claude Code |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/client/multi-de36fa8f59
branch
from
September 26, 2026 02:01
aeded24 to
1ae1103
Compare
3 of 4 tasks
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/client/multi-de36fa8f59
branch
from
September 26, 2026 02:22
1ae1103 to
6ca66d1
Compare
Bumps [react-dom](https://github.com/react/react/tree/HEAD/packages/react-dom) and [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom). These dependencies needed to be updated together. Updates `react-dom` from 18.3.1 to 19.3.0 - [Release notes](https://github.com/react/react/releases) - [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/react/react/commits/v19.3.0/packages/react-dom) Updates `@types/react-dom` from 18.3.7 to 19.3.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom) --- updated-dependencies: - dependency-name: "@types/react-dom" dependency-version: 19.3.0 dependency-type: direct:development update-type: version-update:semver-major - dependency-name: react-dom dependency-version: 19.3.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/client/multi-de36fa8f59
branch
from
September 26, 2026 02:29
6ca66d1 to
32a031e
Compare
This was referenced Sep 27, 2026
koydas
added a commit
that referenced
this pull request
Oct 1, 2026
…me upgrades, grouped bumps) (#184) * ci: test services on the runtime of their Docker image Service test jobs hard-coded Node 20/22 and Python 3.10 while the shipped images run node:26 and python:3.11, and Dependabot only bumps Dockerfiles. Resolve each job's runtime from its Dockerfile (.devops/runtime-version.js) and add a consistency test failing if a service test job hard-codes a runtime version again. Refs #183 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HcKxmDJ1KBXLKgbTxp7Wtx * ci: test database images on an existing data volume Smoke tests only start databases on empty volumes, so a major that cannot open existing data passes CI. On PRs touching databases/** or docker-compose.yml, seed a probe with the base image, restart the same volume with the PR image and read the probe back (mongo, postgres, mssql, root compose mssql). A self-test asserts postgres 16 -> 17 is detected. Refs #183 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HcKxmDJ1KBXLKgbTxp7Wtx * ci(deps): group react and EF Core Dependabot updates react/react-dom and Microsoft.EntityFrameworkCore* only resolve together; split PRs (#175/#179, #176/#178/#180) could never pass on their own. Refs #183 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HcKxmDJ1KBXLKgbTxp7Wtx * ci: require the expected failure in the DB upgrade self-test The self-test accepted any non-zero exit, so an image pull failure or a broken harness would pass as 'incompatible upgrade detected'. The script now exits 3 when the old image cannot store the probe, 4 when the new image exits on the existing data and 5 when it runs but cannot read the probe; the self-test requires exactly 4. Refs #183 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HcKxmDJ1KBXLKgbTxp7Wtx --------- Co-authored-by: Claude <noreply@anthropic.com>
koydas
added a commit
that referenced
this pull request
Oct 1, 2026
Bump react, react-dom, @types/react and @types/react-dom to 19.3 in one change: Dependabot split them into #175 and #179, which can never resolve on their own (ERESOLVE on the 18/19 peer mismatch). The client already uses createRoot and no API removed in React 19, so no source change is needed. Refs #186 Claude-Session: https://claude.ai/code/session_01HcKxmDJ1KBXLKgbTxp7Wtx Co-authored-by: Claude <noreply@anthropic.com>
Owner
|
Superseded by #188 (React 19 migration, merged), which bumps react/react-dom/@types together. Generated by Claude Code |
Contributor
Author
|
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 If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/client/multi-de36fa8f59
branch
October 1, 2026 15:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps react-dom and @types/react-dom. These dependencies needed to be updated together.
Updates
react-domfrom 18.3.1 to 19.3.0Release notes
Sourced from react-dom's releases.
... (truncated)
Changelog
Sourced from react-dom's changelog.
... (truncated)
Commits
f4e439e[Fizz] Addnonceto renderedimport maps(#37339)21c89c9[DOM] Clean up Fragment listeners on signal abort (#37457)065bc84[DOM] Unobserve fragment IntersectionObserver targets after exit (#37408)ff7445e[DOM] Update HTML parser rules for new select parser (#34804)2dc7da7[test] Bump Jest to 30.4 (#37382)29d9d31[DOM] Copysourceonto the synthetic toggle event (#37389)269bd40[test] Remove the customtoThrowoverride for legacy V8 error messages (#37...a112448[DOM] Treat omitted Fragment Event listener options same ascapture: false...3d05080[Fizz] Construct the render lifetime controller only when it is needed (#37357)77ed3f5[Flight/Fizz] Stop the caller's signal from retaining a finished render (#37315)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for react-dom since your current version.
Updates
@types/react-domfrom 18.3.7 to 19.3.0Commits