Remove leftover old-version install strings, fix Next.js minimum - #3537
Closed
eatmorespinach wants to merge 3 commits into
Closed
eatmorespinach wants to merge 3 commits into
eatmorespinach wants to merge 3 commits into
Conversation
Stale v4/v5/v6 version strings on current pages are copyable by readers and by LLMs reading llms-full.txt. GROW-1222 (items 1-5). - Core 3 upgrade guide: reword the Core 2 prep step so `@clerk/nextjs@6` is no longer a copyable install line. - Core 3 upgrade guide: the documented Next.js floor was 15.2.3, but the package's peerDependencies require `^15.2.8` (with a per-release-line patch floor). Corrected in all four places. - Remove the `<Waitlist />` "available in @clerk/nextjs@6.2.0 and above" note from restricting-access, the waitlist guide, and the component reference. Every supported version has it. - Remove the reverification callout partial and its two includes; its entire body was a Core 2 minimum-version list that every supported version now exceeds. - Cognito migration: unpin `npm i -E @clerk/backend@1.4.3`. - usage-with-older-versions: lead with a warning that the page is for Next.js 12 and older only and must not be used for new apps. Core 2 upgrade guides (item 6) and the blog banner (item 7) are not in this change.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
pnpm migrate:clerkRun it locally from the root of this branch and it'll migrate the branch and PR over to The required |
Clarified warning about using Clerk with older Next.js versions.
…version-install-strings
eatmorespinach
marked this pull request as ready for review
September 14, 2026 22:36
SarahSoutoul
changed the title
Contributor
Author
|
This branch and PR were migrated to clerk/clerk. Migration branches/PRs created from this PR (most recent last):
|
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.
A few docs pages still have copyable install strings pinned to
@clerk/nextjsv4/v5/v6. Readers can paste them, and since these pages are inllms-full.txt, LLMs read them too — so they end up seeding new apps on old majors. This clears them out and fixes one version claim that was just wrong.Core 3 upgrade guide, prep step —
npm install @clerk/nextjs@6was a copyable install line on a page people hit mid-upgrade. Reworded to prose so there's nothing to paste.Core 3 upgrade guide, Next.js minimum — the page said 15.2.3 in four places, but
peerDependencies.nextis^15.2.8 || ^15.3.8 || ^15.4.10 || ^15.5.9 || ^15.6.0-0 || ^16.0.10 || ^16.1.0-0(same across 7.0.0 → 7.9.2). So we were telling people a version that fails install. Now 15.2.8.Deliberately not phrased as
next@>=15.2.8— that's wrong too, since 15.3.0 is above 15.2.8 but outside the range. Each line has its own patch floor, so the prose lists them.<Waitlist />version notes — "available in@clerk/nextjs@6.2.0and above" removed fromrestricting-access.mdx,waitlist.mdx, and the component reference. Every supported version has it, so the note just advertises an old version number. Two were wrapped in<If sdk="nextjs">; the empty wrappers went too.Reverification callout — the partial was nothing but a Core 2 minimum-version list (
@clerk/nextjs@6.12.7,@clerk/react@5.25.1,@clerk/clerk-js@5.57.1,@clerk/clerk-sdk-ruby@3.3.0), and every supported version now clears all four. Deleted the partial and both<Include>sites rather than leave an empty warning.Cognito migration guide —
npm i -E @clerk/backend@1.4.3→npm i @clerk/backend. The pin was installing a package two majors behind. The script only usescreateClerkClientandusers.createUser({ emailAddress, passwordDigest, passwordHasher }), both unchanged in v3, so it still works unpinned.usage-with-older-versions.mdx— installs@clerk/nextjs@^4.0.0with no warning above the fold about who it's for. Added one: Next.js 12 and older only, new apps go to the quickstart.Not here: getting the Core 2 upgrade guides out of
llms-full.txt. There's no per-page exclusion mechanism today (listOutputDocsFilestakes every titled page), and the alternative moves live URLs — split to GROW-1238 so it doesn't hold up these copy edits. The blog-banner item is site chrome, tracked separately.Other resources
Verified locally:
pnpm run build:tsxclean (879 docs, no warnings),pnpm run lintgreen across all 15 checks.