feat(nextjs): throw missing-env error instead of keyless bootstrap - #9484
Closed
djgould wants to merge 3 commits into
Closed
feat(nextjs): throw missing-env error instead of keyless bootstrap#9484djgould wants to merge 3 commits into
djgould wants to merge 3 commits into
Conversation
🦋 Changeset detectedLatest commit: 1072f9f The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
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.
|
This was referenced Aug 18, 2026
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-google-signin
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Closed
9 tasks
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Squashed from the original four commits of this PR (bootstrap removal, import sort, adversarial-review findings, non-interactive CLI wording) during the simple-first stack reorder. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
djgould
force-pushed
the
dg/keyless-cli/1-remove-bootstrap
branch
from
August 18, 2026 18:18
1072f9f to
bb7e2a9
Compare
This was referenced Aug 18, 2026
Author
9 tasks
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
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.
Description
Part 1 of the keyless→CLI stack. Experiment: promote the CLI keyless flow over SDK keyless mode.
In development, when
NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY/CLERK_SECRET_KEYare missing,@clerk/nextjsno longer provisions a keyless application. All three bootstrap entry points (app-router serverClerkProvider,clerkMiddleware,createOrReadKeylessAction) now throw acode=missing_env_keyserror directing to:The message states the command is non-interactive and requires no Clerk account or login (sandbox agent trials showed agents otherwise route around the CLI or invent placeholder keys). The error surfaces in both the dev server log and the dev error page. Configured keys, claimed keys, and production behavior are unchanged.
Supersedes #9474 (same content, restacked fresh off main).
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
🤖 Generated with Claude Code