Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@steven-tey
Copy link
Collaborator

@steven-tey steven-tey commented Dec 6, 2025

Summary by CodeRabbit

  • Chores
    • Updated React ecosystem dependencies to 19.1.2 across multiple packages.
    • Bumped core and React embed package versions to 0.0.17.
    • Locked React/ReactDOM peer dependency versions to exact 19.1.2 specifications.

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link
Contributor

vercel bot commented Dec 6, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
dub Ready Ready Preview Dec 6, 2025 10:51pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 6, 2025

Walkthrough

Packages have updated version numbers and React-related dependency pins: core embed bumped to 0.0.17; embeds/react, stripe-app, and utils moved React/react-dom/@types to 19.1.2 (utils peerDependencies locked to exact 19.1.2). No source logic changes.

Changes

Cohort / File(s) Summary
Core package version
packages/embeds/core/package.json
version bumped 0.0.160.0.17.
Embeds React package
packages/embeds/react/package.json
version bumped 0.0.160.0.17; peerDependencies.react & peerDependencies.react-dom ^18.2.019.1.2; devDependencies.react, @types/react, @types/react-dom updated to 19.1.2.
Stripe app dependency pins
packages/stripe-app/package.json
react, react-dom pinned/updated to 19.1.2 (was ^19.0.0); @types/react, @types/react-dom updated to 19.1.2.
Utils peer dependency locking
packages/utils/package.json
peerDependencies.react and peerDependencies.react-dom changed from ^19.1.2 → exact 19.1.2.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Mostly homogeneous dependency/version changes across package manifests.
  • Review attention recommended for:
    • packages/embeds/react/package.json — verify peer/dev dependency alignment with build/test setup.
    • packages/utils/package.json — confirm exact peer version won't break consumers expecting caret range.
    • packages/stripe-app/package.json — check app build/test against React 19.1.2.

Poem

🐰 I hopped through package.json land,
nudged versions with a careful hand.
From eighteen to nineteen, snug and true,
pins set tight, dependencies new.
A tiny thump — a joyous tune,
carrots and commits beneath the moon. 🌙

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: standardizing React dependencies across multiple packages to consistent versions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix-deps

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between be48ee1 and 87b6580.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (4)
  • packages/embeds/core/package.json (1 hunks)
  • packages/embeds/react/package.json (2 hunks)
  • packages/stripe-app/package.json (2 hunks)
  • packages/utils/package.json (1 hunks)
🔇 Additional comments (4)
packages/embeds/core/package.json (1)

4-4: Version bump is appropriate. Package version updated from 0.0.16 to 0.0.17, aligning with related embed packages.

packages/utils/package.json (1)

20-21: Verify dev/peer dependency consistency for React types.

PeerDependencies are pinned exactly ([email protected], [email protected]), while devDependencies retain caret specifiers (react@^19.1.2). Additionally, @types/react@^19.1.15 (line 27) is a newer minor/patch version than the peered React 19.1.2. This split approach requires verification to ensure type definitions remain aligned with the runtime across all dependency resolution scenarios, especially in consumer projects that depend on @dub/utils.

Also applies to: 29-29

packages/embeds/react/package.json (1)

21-22: Verify React 19 compatibility for source code changes.

This file pins a major version upgrade: React 18.2.0 → React 19.1.2. React 19 introduces breaking changes including removed/deprecated APIs (propTypes for functions, string refs, createFactory), JSX transform requirements, and error handling behavior changes. Exact version pinning is appropriate for this change, but ensure all source code in packages/embeds/react/src/** has been updated to comply with React 19 APIs and remove any deprecated patterns.

Also applies to: 25-26, 29-29

packages/stripe-app/package.json (1)

9-10: Verify React 19.1.2 compatibility with Stripe UI Extension SDK.

The @stripe/ui-extension-sdk@^8.8.1 (line 8) may have peer dependency or internal assumptions about React versions. Confirm that this SDK version is compatible with React 19.1.2 or upgrade the SDK if needed.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​types/​react-dom@​19.1.21001007493100
Added@​types/​react@​19.1.21001008095100

View full report

@steven-tey
Copy link
Collaborator Author

@coderabbitai full review

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 6, 2025

✅ Actions performed

Full review triggered.

@steven-tey steven-tey merged commit 2645eab into main Dec 6, 2025
7 of 8 checks passed
@steven-tey steven-tey deleted the fix-deps branch December 6, 2025 23:08
@coderabbitai coderabbitai bot mentioned this pull request Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants