-
Notifications
You must be signed in to change notification settings - Fork 2.1k
chore(deps): bump react-dom and @types/react-dom in /examples/non-monorepo #10903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): bump react-dom and @types/react-dom in /examples/non-monorepo #10903
Conversation
Bumps [react-dom](https://github.com/facebook/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 19.1.0 to 19.1.1 - [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.1.1/packages/react-dom) Updates `@types/react-dom` from 19.1.6 to 19.1.9 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom) --- updated-dependencies: - dependency-name: react-dom dependency-version: 19.1.1 dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: "@types/react-dom" dependency-version: 19.1.9 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
| "next": "15.4.6", | ||
| "react": "^19.1.0", | ||
| "react-dom": "^19.1.0", | ||
| "react-dom": "^19.1.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The package.json was updated to require react-dom@^19.1.1 and @types/react-dom@^19.1.9, but the corresponding pnpm-lock.yaml lockfile was not updated and still references the old versions (19.1.0 and 19.1.6 respectively).
View Details
📝 Patch Details
diff --git a/examples/non-monorepo/pnpm-lock.yaml b/examples/non-monorepo/pnpm-lock.yaml
index 6eb26b874..c830a86b6 100644
--- a/examples/non-monorepo/pnpm-lock.yaml
+++ b/examples/non-monorepo/pnpm-lock.yaml
@@ -7,13 +7,13 @@ settings:
dependencies:
next:
specifier: 15.4.6
- version: 15.4.6(react-dom@19.1.0)(react@19.1.0)
+ version: 15.4.6(react-dom@19.1.1)(react@19.1.0)
react:
specifier: ^19.1.0
version: 19.1.0
react-dom:
- specifier: ^19.1.0
- version: 19.1.0(react@19.1.0)
+ specifier: ^19.1.1
+ version: 19.1.1(react@19.1.0)
turbo:
specifier: ^2.5.4
version: 2.5.4
@@ -29,8 +29,8 @@ devDependencies:
specifier: ^19.1.6
version: 19.1.8
'@types/react-dom':
- specifier: ^19.1.6
- version: 19.1.6(@types/react@19.1.8)
+ specifier: ^19.1.9
+ version: 19.1.9(@types/react@19.1.8)
eslint:
specifier: ^9.33.0
version: 9.33.0
@@ -534,8 +534,8 @@ packages:
undici-types: 6.21.0
dev: true
- /@types/react-dom@19.1.6(@types/react@19.1.8):
- resolution: {integrity: sha512-4hOiT/dwO8Ko0gV1m/TJZYk3y0KBnY9vzDh7W+DH17b2HFSOGgdj33dhihPeuy3l0q23+4e+hoXHV6hCC4dCXw==}
+ /@types/react-dom@19.1.9(@types/react@19.1.8):
+ resolution: {integrity: sha512-qXRuZaOsAdXKFyOhRBg6Lqqc0yay13vN7KrIg4L7N4aaHN68ma9OK3NE1BoDFgFOTfM7zg+3/8+2n8rLUH3OKQ==}
peerDependencies:
'@types/react': ^19.0.0
dependencies:
@@ -2252,7 +2252,7 @@ packages:
resolution: {integrity: sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==}
dev: true
- /next@15.4.6(react-dom@19.1.0)(react@19.1.0):
+ /next@15.4.6(react-dom@19.1.1)(react@19.1.0):
resolution: {integrity: sha512-us++E/Q80/8+UekzB3SAGs71AlLDsadpFMXVNM/uQ0BMwsh9m3mr0UNQIfjKed8vpWXsASe+Qifrnu1oLIcKEQ==}
engines: {node: ^18.18.0 || ^19.8.0 || >= 20.0.0}
hasBin: true
@@ -2278,7 +2278,7 @@ packages:
caniuse-lite: 1.0.30001723
postcss: 8.4.31
react: 19.1.0
- react-dom: 19.1.0(react@19.1.0)
+ react-dom: 19.1.1(react@19.1.0)
styled-jsx: 5.1.6(react@19.1.0)
optionalDependencies:
'@next/swc-darwin-arm64': 15.4.6
@@ -2467,10 +2467,10 @@ packages:
resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==}
dev: true
- /react-dom@19.1.0(react@19.1.0):
- resolution: {integrity: sha512-Xs1hdnE+DyKgeHJeJznQmYMIBG3TKIHJJT95Q58nHLSrElKlGQqDTR2HQ9fx5CN/Gk6Vh/kupBTDLU11/nDk/g==}
+ /react-dom@19.1.1(react@19.1.0):
+ resolution: {integrity: sha512-Dlq/5LAZgF0Gaz6yiqZCf6VCcZs1ghAJyrsu84Q/GT0gV+mCxbfmKNoGRKBYMJ8IEdGPqu49YWXD02GCknEDkw==}
peerDependencies:
- react: ^19.1.0
+ react: ^19.1.1
dependencies:
react: 19.1.0
scheduler: 0.26.0
Analysis
Outdated pnpm lockfile in examples/non-monorepo
What fails: The pnpm-lock.yaml file in examples/non-monorepo/ has outdated specifiers and versions for react-dom (^19.1.0 → ^19.1.1) and @types/react-dom (^19.1.6 → ^19.1.9) that don't match the updated package.json.
How to reproduce:
cd examples/non-monorepo
# Check semver compatibility
node -e "const semver = require('semver'); console.log('19.1.0 satisfies ^19.1.1:', semver.satisfies('19.1.0', '^19.1.1'));"
# Returns: false
# Install with workspace isolation
pnpm install --ignore-workspaceResult: pnpm installs the updated versions (react-dom@19.1.1 and @types/react-dom@19.1.9) because the lockfile specifiers don't match package.json requirements. The lockfile is regenerated with the correct specifiers.
Expected: Lockfile should have been updated when package.json dependencies were changed. The version 19.1.0 doesn't satisfy the semver range ^19.1.1, creating an inconsistency between package.json and pnpm-lock.yaml.
Fix: Ran pnpm install --ignore-workspace in examples/non-monorepo/ to regenerate the lockfile with correct specifiers and versions matching the package.json requirements.
|
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. |
Bumps react-dom and @types/react-dom. These dependencies needed to be updated together.
Updates
react-domfrom 19.1.0 to 19.1.1Release notes
Sourced from react-dom's releases.
Changelog
Sourced from react-dom's changelog.
Commits
87e33caSet release versions to 19.1.1b793948Bump next prerelease version numbers (#32782)Updates
@types/react-domfrom 19.1.6 to 19.1.9Commits
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)