-
Notifications
You must be signed in to change notification settings - Fork 406
feat(nextjs): Drop support for next v13 and v14 #7197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(nextjs): Drop support for next v13 and v14 #7197
Conversation
🦋 Changeset detectedLatest commit: 21e6043 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
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 You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
|
!allow-major |
Description
This PR raises the minimum supported Next.js version to 15.2.3, removing most legacy compatibility code for Next.js 13 and 14.
startTransitionwrapper aroundrouter.refresh()that was only needed for Next.js 13. Dropped the__clerk_internal_invalidateCachePromisemechanism that coordinated promise resolution with transition state. Removed theisPendingstate tracking fromuseTransitionsince we no longer wrap operations in transitions. The __unstable__onBeforeSetActive hook now directly calls invalidateCacheAction() (or skips it for Next.js 15+ sign-outs).useInternalNavFunfor handling shallow routing stateChecklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change