revert: Dependabot #90 — Next.js 16 + Fumadocs 16 breaks the website build#116
Conversation
|
Caution Review failedThe pull request is closed. Note
|
| Layer / File(s) | Summary |
|---|---|
Production and development dependency versions website/package.json |
Updates dependencies and devDependencies with new version constraints for framework, UI libraries, and development tooling including next, react types, eslint, and typescript. |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~8 minutes
✨ Finishing Touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Commit unit tests in branch
revert/90-next16-fumadocs16-break
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 help to get the list of available commands and usage tips.
…next/fumadocs/react majors (#118) PR #90 grouped next 15->16 + fumadocs 15->16 into one auto-bump that broke the website build (fumadocs-ui/provider export moved in v16); reverted in #116. - The website npm group now only bundles minor + patch updates. Majors get their own individual, individually-testable PRs. - next / fumadocs-{core,ui,mdx} / react / react-dom majors are ignored entirely — those require a coordinated migration (Fumadocs v16 needs Next 16 + React 19 export-path changes), which is a deliberate project, not an auto-merge.
Why
Reverts #90 (
87a8152f). That grouped Dependabot bump pushed next 15.5.18 → 16.2.6 and fumadocs-{core,ui} 15 → 16 + fumadocs-mdx 13 → 15 together. Fumadocs 16 restructured its package exports, so the build fails:The Cloudflare Pages check failed on the original PR — for a website-dependency PR that build IS the validation, and it was mis-merged by treating the Cloudflare failure as non-blocking preview noise. This restores the known-good Next 15 / Fumadocs 15 stack.
Verified
nextback to^15.5.15, fumadocs back to 15.npx next build→ ✓ Compiled, 80/80 static pages, ✓ Exporting (2/2). Green.The Next 16 / Fumadocs 16 upgrade is a real project, not an auto-merge
It needs the deliberate migration (fumadocs 16 export-path changes, Next 16 config + React 19 surface). Tracking as a separate task; Dependabot should be configured to ignore next + fumadocs majors so it stops re-proposing this grouped break.
Summary by CodeRabbit