Uh oh!
There was an error while loading. Please reload this page.
fix(clerk-js): dev browser partitioned cookie cleanup - #8538
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 1de724c 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 |
📝 WalkthroughWalkthroughThis PR centralizes dev-browser cookie deletion by adding a fixed partitioned-attributes constant and a removeAll() helper that clears suffixed and unsuffixed cookie variants (current attrs, no attrs, and fixed partitioned attrs). set() now calls removeAll() before writing, and remove() delegates to removeAll(). A Vitest suite with a mocked in-memory cookie handler verifies remove(), set(), and get() behaviors and deterministic cookie attribute assertions. Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
@clerk/astro@clerk/backend@clerk/chrome-extension@clerk/clerk-js@clerk/dev-cli@clerk/expo@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/vuecommit: |
Summary
This bug was discovered due to reports of stale dev browser cookies when switching between instances that use partitioned cookies. During clerk-js initialization, we do not properly clear stale dev browser cookies that are partitioned.
Tests