Repository navigation
chore(deps-dev): bump react from 19.3.0 to 19.3.1 - #944
Conversation
dependabot
Bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Thanks @dependabot[bot] for keeping our dependencies current! 🙌 |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Added aea153d: |
Bumps [react](https://github.com/react/react/tree/HEAD/packages/react) from 19.3.0 to 19.3.1. - [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.1/packages/react) --- updated-dependencies: - dependency-name: react dependency-version: 19.3.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
react-dom/client throws "Incompatible React versions" at import unless `react` and `react-dom` are the exact same version, so bumping react to 19.3.1 alone fails every test file that renders: 25 test files failed on this PR against 1 on main. #907 (react-dom alone) was closed for the same reason in reverse, so Dependabot will not propose react-dom 19.3.1 again; it moves here, with react. bun.lock only: react-dom 19.3.1 keeps `scheduler ^0.28.0` and peers on `react ^19.3.1`. `bun install --frozen-lockfile` accepts it and a plain `bun install` leaves the lock byte-identical. With it, the unit suite fails only the four fixture-pin cases #950 fixes on main. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01KYzGfVxwGZMvdyyi97XyZY
aea153d to
f29fd7b
Compare
Bumps react from 19.3.0 to 19.3.1.
Release notes
Sourced from react's releases.
Commits
61aa00d[19.3.x][Flight] Improve transport protocol (#37845)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)