fix(shared): classify local production keys as live - #9633
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: b2874b7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 23 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 |
@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: |
API Changes Report
Summary
@clerk/fastifyCurrent version: 3.1.74 Subpath
|
Description
Local production Frontend API hosts under
.prod.lclclerk.comcurrently get apk_test_key because publishable-key generation treats every.lclclerk.comhost as development. This makes ClerkJS load a production system instance as development and require a dev browser. This change excludes local production hosts from the legacy development rule while keeping existing development host behavior.Run
pnpm --filter @clerk/shared test -- src/__tests__/keys.spec.tsto verify the production and development host cases.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change