fix(dashboard): sync pnpm-lock.yaml with next@14.2.35 — unblocks Vercel deploy - #117
Conversation
…l deploy) #114 bumped next 14.2.15→14.2.35 in package.json via npm, so pnpm-lock.yaml stayed at 14.2.15. Vercel builds with 'pnpm install --frozen-lockfile' → ERR_PNPM_OUTDATED_LOCKFILE (lockfile 14.2.15 ≠ manifest 14.2.35) → production build failed. Regenerated the lock with pnpm 10 so frozen-install matches. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
paycraft-docs | 895f8e2 | Jul 14 2026, 11:33 AM |
1 participant
Vercel production build is failing with
ERR_PNPM_OUTDATED_LOCKFILE:#114 bumped Next.js in
package.jsonvia npm, leavingpnpm-lock.yamlat 14.2.15. Vercel usespnpm install --frozen-lockfile, so it rejects the mismatch. Regenerated the lock with pnpm 10 (next@14.2.35). Merging this makes the next Vercel deploy succeed with the current code.🤖 Generated with Claude Code