chore(deps): bump react-dom from 19.2.6 to 19.2.7#45
Conversation
Bumps [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) from 19.2.6 to 19.2.7. - [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.7/packages/react-dom) --- updated-dependencies: - dependency-name: react-dom dependency-version: 19.2.7 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
📝 WalkthroughWalkthroughThis PR updates the ChangesReact DOM Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/web/package.json`:
- Line 29: Update the pinned React versions so they match: in apps/web's
package.json change the "react" entry to the same version as "react-dom"
(19.2.7) to satisfy peerDependencies and avoid the lockfile mismatch; after
updating the "react" dependency, run the workspace package manager (pnpm
install) to regenerate pnpm-lock.yaml and verify no peer dependency warnings for
react-dom@19.2.7 referencing react.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 47225899-e038-4a36-8dbd-2406259d8a1d
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
apps/web/package.json
| "next": "16.2.6", | ||
| "react": "19.2.6", | ||
| "react-dom": "19.2.6", | ||
| "react-dom": "19.2.7", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify current manifest versions and lockfile peer contract (read-only).
set -euo pipefail
echo "apps/web/package.json React lines:"
rg -n '"react"|"react-dom"' apps/web/package.json -n -C1
echo
echo "pnpm-lock.yaml importer resolution lines:"
rg -n 'react-dom:|react:' pnpm-lock.yaml -n -C2 | head -n 40
echo
echo "pnpm-lock.yaml peerDependencies for react-dom@19.2.7:"
rg -n 'react-dom@19\.2\.7|peerDependencies|react:\s+\^19\.2\.7' pnpm-lock.yaml -n -C3Repository: OpenDevFlow/md-latex
Length of output: 20060
Align react version with react-dom in apps/web/package.json.
apps/web/package.json pins react-dom to 19.2.7 while react remains 19.2.6. In pnpm-lock.yaml, react-dom@19.2.7 declares peerDependencies: react: ^19.2.7, but the lockfile resolves react-dom@19.2.7(react@19.2.6), creating a peer mismatch.
🔧 Suggested fix
- "react": "19.2.6",
+ "react": "19.2.7",
"react-dom": "19.2.7",🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/web/package.json` at line 29, Update the pinned React versions so they
match: in apps/web's package.json change the "react" entry to the same version
as "react-dom" (19.2.7) to satisfy peerDependencies and avoid the lockfile
mismatch; after updating the "react" dependency, run the workspace package
manager (pnpm install) to regenerate pnpm-lock.yaml and verify no peer
dependency warnings for react-dom@19.2.7 referencing react.
Bumps react-dom from 19.2.6 to 19.2.7.
Release notes
Sourced from react-dom's releases.
Commits
6117d7cVersion 19.2.7 (#36591)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for react-dom since your current version.
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)Summary by CodeRabbit