Repository navigation
Conversation
🦋 Changeset detectedLatest commit: 0baee80 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 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.
|
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-biometrics
@clerk/expo-google-signin
@clerk/expo-native-components
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/mosaic
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
mwickett
changed the title
This branch was successfully deployed
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
@clerk/chrome-extensionuses ClerkJS's no-RHC build, but that build could still insert Device Intelligence scripts supplied by the environment configuration. The no-RHC build now omits Device Intelligence loader initialization. Regular browser builds retain the configured loading behavior.Production extension requests also declare native API mode from the first request, before a client credential is stored. Previously, only requests with a cached credential included that mode, preventing a fresh production extension from initializing authentication.
Build checks cover both ESM and CommonJS no-RHC outputs. Packaged-extension regressions exercise configured remote and inline script loaders with extension CSP enforced. The live auth suite covers development and production sign-in and sign-up without a Testing Token. It uses reserved verification addresses, creates disposable users, and removes its temporary production origin afterward. On the dedicated production fixture, email verification temporarily uses test mode and restores the original setting after the test.
The draft remains blocked on development sign-up: the live test receives an HTTP 403 response. Development sign-in and production sign-in/sign-up pass.
Checklist
pnpm turbo build --filter=@clerk/chrome-extension --concurrency=3passes, including both no-RHC artifact checks.Type of change