Update Money Dev Kit to 0.18.0#17
Open
sbddesign wants to merge 1 commit into
Open
Conversation
Bump @moneydevkit/nextjs from ^0.16.0 to ^0.18.0. No code changes required — the bump is a drop-in (the 0.17.0/0.18.0 changes to MDK's server helpers are additive and the SettleResult type our code uses is unchanged). Build verified successful.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThe PR updates the ChangesDependency Version Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 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)
⚔️ Resolve merge conflicts
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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 `@package.json`:
- Line 16: Update runtime verification after bumping "`@moneydevkit/nextjs`" to
^0.18.0 by performing a focused smoke test: install dependencies and run the
app, then exercise payment flows end-to-end — create a checkout and confirm
redirect behavior, verify client hooks/useCheckoutSuccess return expected
success state in post-checkout pages, and validate server/client behavior of
withDeferredSettlement (deferred settlement callbacks and webhooks) against your
payment sandbox; if any behavioral/API differences appear, pin or adapt code
paths referencing useCheckoutSuccess, withDeferredSettlement, and checkout
creation/redirect handling to match the new package's contract.
🪄 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
Run ID: 4118fd3d-d951-4dc7-9dfc-b2004cd0b439
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
package.json
| }, | ||
| "dependencies": { | ||
| "@moneydevkit/nextjs": "^0.16.0", | ||
| "@moneydevkit/nextjs": "^0.18.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check npm registry for `@moneydevkit/nextjs` version 0.18.0 and any security info
echo "=== Checking version 0.18.0 exists ==="
npm view `@moneydevkit/nextjs`@0.18.0 version
echo -e "\n=== Checking for security advisories ==="
npm audit --json --package-lock-only 2>/dev/null | jq '.vulnerabilities // "No vulnerabilities found in audit"'
echo -e "\n=== Checking latest version ==="
npm view `@moneydevkit/nextjs` version
echo -e "\n=== Checking peer dependencies for 0.18.0 ==="
npm view `@moneydevkit/nextjs`@0.18.0 peerDependenciesRepository: ATLBitLab/freeport
Length of output: 827
@moneydevkit/nextjs 0.18.0 bump: security check looks clean; still smoke-test payment runtime
@moneydevkit/nextjs@0.18.0exists on npm and its peer deps align with Next/React (next '^15 || ^16',react '^18 || ^19',react-dom '^18 || ^19').npm auditreports no known vulnerabilities.- Build success covers compile-time compatibility, but validate runtime payment flows (checkout create+redirect,
useCheckoutSuccess, andwithDeferredSettlement) to catch any behavioral/API contract changes.
🤖 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 `@package.json` at line 16, Update runtime verification after bumping
"`@moneydevkit/nextjs`" to ^0.18.0 by performing a focused smoke test: install
dependencies and run the app, then exercise payment flows end-to-end — create a
checkout and confirm redirect behavior, verify client hooks/useCheckoutSuccess
return expected success state in post-checkout pages, and validate server/client
behavior of withDeferredSettlement (deferred settlement callbacks and webhooks)
against your payment sandbox; if any behavioral/API differences appear, pin or
adapt code paths referencing useCheckoutSuccess, withDeferredSettlement, and
checkout creation/redirect handling to match the new package's contract.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
@moneydevkit/nextjsfrom^0.16.0to^0.18.0(latest).Details
programmaticPayout()andgetBalance()server helpers we don't use. The one internal type rename (PaymentConfig→WithPaymentConfig) doesn't affect us: ourwithDeferredSettlementcall still type-checks, and theSettleResulttype we import is unchanged.next,react,react-dom) are identical across 0.16–0.18; no other bumps needed.MDK_ACCESS_TOKEN,MDK_MNEMONIC) unchanged.Testing
pnpm build✅ — TypeScript compiles, all 27 routes generated, no errors.Summary by CodeRabbit
@moneydevkit/nextjsto a newer compatible version.