Conversation
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
WalkthroughThree package.json files were edited to bump devDependency versions: packages/kg-html-to-lexical updated Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2d38ad3 to
493b8ec
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@packages/kg-unsplash-selector/package.json`:
- Around line 37-38: The package.json has a React version mismatch: `@types/react`
and `@types/react-dom` are pinned to 19.x while peerDependencies list React
^18.2.0; fix by making the types and peerDependencies consistent — either
downgrade "@types/react" and "@types/react-dom" to 18.x to match the existing
peerDependencies or update the peerDependencies (react, react-dom) to ^19.x to
match the types. Locate the dependency keys "@types/react", "@types/react-dom"
and the peerDependencies entries "react" and "react-dom" in package.json and
update their versions accordingly, then run a quick build/typecheck to confirm
no type errors remain.
| "@types/react": "19.2.9", | ||
| "@types/react-dom": "19.2.3", |
There was a problem hiding this comment.
Major version mismatch: @types/react@19 with React 18 peer dependencies.
The type definitions are updated to React 19.x, but the peerDependencies at lines 32-33 declare compatibility with React ^18.2.0. This inconsistency means:
- Consumers installing this package with React 18 (as the peer deps suggest) will have type definitions that don't match their runtime
- TypeScript may report errors for React 19 type patterns that don't exist in React 18
Either update the peer dependencies to React 19, or keep the type definitions at 18.x to match the declared compatibility.
Also applies to: 31-34
🤖 Prompt for AI Agents
In `@packages/kg-unsplash-selector/package.json` around lines 37 - 38, The
package.json has a React version mismatch: `@types/react` and `@types/react-dom` are
pinned to 19.x while peerDependencies list React ^18.2.0; fix by making the
types and peerDependencies consistent — either downgrade "@types/react" and
"@types/react-dom" to 18.x to match the existing peerDependencies or update the
peerDependencies (react, react-dom) to ^19.x to match the types. Locate the
dependency keys "@types/react", "@types/react-dom" and the peerDependencies
entries "react" and "react-dom" in package.json and update their versions
accordingly, then run a quick build/typecheck to confirm no type errors remain.
d36ea35 to
55a2d68
Compare
3cba510 to
f41a51a
Compare
f42da6c to
3ac7915
Compare
3ac7915 to
003a48c
Compare
This PR contains the following updates:
21.1.7→27.0.018.3.27→19.2.1018.3.7→19.2.3Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.