Skip to content

Upgrade to Next 16 + React 19#1

Closed
MaxGhenis wants to merge 2 commits into
mainfrom
upgrade-next-16-tw4
Closed

Upgrade to Next 16 + React 19#1
MaxGhenis wants to merge 2 commits into
mainfrom
upgrade-next-16-tw4

Conversation

@MaxGhenis
Copy link
Copy Markdown
Contributor

Summary

  • Upgrade next from ^14.2 to ^16 (resolved to 16.1.6)
  • React was already at ^19.2.3, no change needed
  • Tailwind 4 already in place, no changes needed
  • Build passes cleanly with Turbopack

Test plan

  • bun run build succeeds with no errors
  • Verify Vercel deployment works

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 6, 2026

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

Project Deployment Actions Updated (UTC)
snap-bbce-repeal Ready Ready Preview, Comment Mar 7, 2026 1:49pm

Request Review

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@MaxGhenis
Copy link
Copy Markdown
Contributor Author

Closing as stale (2 months without updates and likely conflicts with main). The framework upgrade goal here — Next 14 → 16, React 18 → 19, Tailwind 3 → 4 — is still valid and overlaps with the broader Next-modernization sweep happening across the org (see policyengine-ui-kit#28 → 0.8.0+0.9.0 and the consumer rollout). I'll re-open a fresh PR on top of current main when this repo's turn comes up. If you want it sooner, ping me.

@MaxGhenis MaxGhenis closed this May 9, 2026
@MaxGhenis MaxGhenis deleted the upgrade-next-16-tw4 branch May 9, 2026 16:00
@MaxGhenis MaxGhenis mentioned this pull request May 9, 2026
5 tasks
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.

1 participant