Repository navigation
Fix production auth cutover and retire cached Clerk frontend - #335
Conversation
Maple review🟢 Confidence 8/10 · likely safe to merge Requests openid/email/profile from Google explicitly and switches the Maple dashboard widget/query draft fields to the v2 snake_case wire format. Contained and safe to merge; no defect found in either hunk. Before merge
What was checked
|
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 2
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
|
Warning The review of |
|
Merged with 2 steps from "Before merge" still open. If they are done, tick them on the review comment; if not, now is the time.
|
Production cutover exposed three issues: Google requested only openid, Maple dashboard widgets used camelCase instead of the v2 wire format, and existing browsers retained the React/Clerk Workbox service worker.
Request openid, email, and profile explicitly, use snake_case dashboard fields, and serve a retirement worker at /sw.js. On activation it removes Workbox caches, unregisters itself, and reloads controlled Hazel windows onto Foldkit. Application storage and session cookies are preserved.
Validation: auth and Alchemy typechecks passed; the initial fixes were deployed and API health, sessions, JWKS, provider initiation, and frontend artifacts checked. Retirement-worker syntax passed and was deployed to production. Verified in the user's Arc browser that the previously stuck loader now reaches the workspace list, including Hazel and Maple.