@clerk/clerk-js@6.25.0
📦 clerkView on GitHub →
✨ 4 features🔧 5 symbols
Summary
This release introduces support for Clerk Protect mid-flow SDK challenges during sign-up and sign-in flows, adding a new status value and corresponding fields to handle iterative challenges.
Migration Steps
- If using an exhaustive `switch` on `signIn.status`, handle the new `'needs_protect_check'` value by running the challenge described by `protectCheck` and submitting the proof via `submitProtectCheck()`.
✨ New Features
- Add support for Clerk Protect mid-flow SDK challenges (`protect_check`) on both sign-up and sign-in.
- Responses now carry a `protectCheck` field with `{ status, token, sdkUrl, expiresAt?, uiHints? }` when a Protect antifraud service challenge is issued.
- Sign-in adds a new `'needs_protect_check'` value to the `SignInStatus` union.
- Pre-built `<SignIn />` and `<SignUp />` components automatically handle the Protect gate by routing to a new `protect-check` route.