Releases: clerk/javascript
Release list
@clerk/vue@2.4.32
Choose a tag to compare
Sorry, something went wrong.
No results found
@clerk/ui@1.30.7
Choose a tag to compare
Sorry, something went wrong.
No results found
Patch Changes
-
Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @jeremy-clerk
Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.
-
Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @zourzouvillys
-
Route an OAuth transfer to the sign-up continue step when sign-in uses a native OAuth transport. The callback previously navigated with hash-style URLs (<sign-up-url>#/continue) that the in-place component router cannot resolve, landing transferred sign-ups on the start card where submitting created a fresh sign-up without the verified external account. (#9530) by @jeremy-clerk
-
Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @zourzouvillys
-
Updated dependencies [28b77ac, 46bf7ce, 8bc1c9f, 17b865b]:
- @clerk/shared@4.30.0
- @clerk/localizations@4.15.6
@clerk/testing@2.2.29
Choose a tag to compare
Sorry, something went wrong.
No results found
@clerk/tanstack-react-start@1.5.7
Choose a tag to compare
Sorry, something went wrong.
No results found
@clerk/shared@4.30.0
Choose a tag to compare
Sorry, something went wrong.
No results found
Minor Changes
- Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @zourzouvillys
Patch Changes
-
Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @jeremy-clerk
Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.
-
Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @eatmorespinach
-
Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @zourzouvillys