fix(clerk-js): Backport iframe __client_uat cookie domain fix#7882
Conversation
…xts (#7875) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 27019fe The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 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.
|
|
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 Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/elements
@clerk/clerk-expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/clerk-react
@clerk/react-router
@clerk/remix
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/themes
@clerk/types
@clerk/upgrade
@clerk/vue
commit: |
Summary
release/core-2__client_uatcookie being set on two different domain scopes when app is loaded in both iframe and non-iframe contextsgetCookieDomain()now falls back tohostnameinstead ofundefinedwhen the eTLD+1 probe fails, and the probe uses the sameSameSite/Secureattributes as the actual cookieTest plan
getCookieDomaintests pass__client_uatcookie is set correctly in iframe and non-iframe contexts🤖 Generated with Claude Code