javascript

Patch Changes

• Updated dependencies [ec84d51e7]:
  • @clerk/[email protected]
  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• Added missing phpass and bcrypt_sha256_django hashers to PasswordHasher type (#3380) by @royanger

• Updated dependencies [ec84d51e7]:

  • @clerk/[email protected]

Patch Changes

• Updated dependencies [fce528bf6, fce528bf6]:
  • @clerk/[email protected]

Patch Changes

• Improve logging for CAPTCHA script loading errors (#3384) by @anagstef

• Fix Cypress setting cookies as third-party (#3384) by @anagstef

Patch Changes

• Updated dependencies [fce528bf6, fce528bf6]:
  • @clerk/[email protected]

Minor Changes

• Updates related to experimental Google One Tap support (#3250) by @panteliselef

  • By default we are returning back to the location where the flow started.
    To accomplish that internally we will use the redirect_url query parameter to build the url.

  <__experimental_GoogleOneTap />
  

  • In the above example if there is a SIGN_UP_FORCE_REDIRECT_URL or SIGN_IN_FORCE_REDIRECT_URL set then the developer would need to pass new values as props like this

  <__experimental_GoogleOneTap
    signInForceRedirectUrl=''
    signUpForceRedirectUrl=''
  />
  

  • Let the developer configure the experience they want to offer. (All these values are true by default)

  <__experimental_GoogleOneTap
    cancelOnTapOutside={false}
    itpSupport={false}
    fedCmSupport={false}
  />
  

  • Moved authenticateWithGoogleOneTap to Clerk singleton

  Clerk.__experimental_authenticateWithGoogleOneTap;
  

  • Created the handleGoogleOneTapCallback in Clerk singleton

  Clerk.__experimental_handleGoogleOneTapCallback;
  

• Introduce new client_mismatch verification status for email link sign-in and sign-up. This error (and its message) will be shown if a verification link was opened in another device/browser from which the user initiated the sign-in/sign-up attempt. This functionality needs to be enabled in the Clerk dashboard. (#3367) by @mzhong9723

Patch Changes

• Updated dependencies [94197710a, b27ca8366]:
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [94197710a, b27ca8366]:
  • @clerk/[email protected]
  • @clerk/[email protected]

Minor Changes

• Introduce new client_mismatch verification status for email link sign-in and sign-up. This error (and its message) will be shown if a verification link was opened in another device/browser from which the user initiated the sign-in/sign-up attempt. This functionality needs to be enabled in the Clerk dashboard. (#3367) by @mzhong9723

Patch Changes

• Updated dependencies [b27ca8366]:
  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [b27ca8366, bcbb2c9ef]:
  • @clerk/[email protected]
  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• Respect the signInForceRedirectUrl, signInFallbackRedirectUrl, signUpForceRedirectUrl and signUpFallbackRedirectUrl props passed to SignInButton, SignUpButton and the low-level window.Clerk.buildSignInUrl & window.Clerk.buildSignUpUrl methods. These props allow you to control the redirect behavior of the SignIn and SignUp components. For more information, refer to the Custom Redirects guide. (#3361) by @nikosdouvlis

• Updated dependencies [94197710a, b27ca8366]:

  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [b27ca8366, bcbb2c9ef]:
  • @clerk/[email protected]
  • @clerk/[email protected]
  • @clerk/[email protected]

Minor Changes

• Add srRS localization (#3338) by @paunovic5ar

• Added new keys for email link verification under signIn.emailLink.clientMismatch and signUp.emailLink.clientMismatch (#3367) by @mzhong9723

Patch Changes

• Update esMX language module (#3372) by @Thiagoamaro2431

Patch Changes

• Updated dependencies [94197710a, b27ca8366]:
  • @clerk/[email protected]
  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [b27ca8366]:
  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [94197710a, 34befeebc, b27ca8366, bcbb2c9ef]:
  • @clerk/[email protected]
  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• This release includes various smaller fixes and one dependency update: (#3343) by @tmilewski

  • xstate was updated from 5.12.0 to 5.13.0
  • Previously, the contents of the fallback prop were sometimes shown even if the user wasn't on the start step. This bug is fixed now.
  • Upon completion of an sign-in/sign-up attempt, don't immediately return to the start step. This fixes the issue of a "flash of content" that could e.g. be seen during sign-in with OAuth providers.
  • Some underlying fixes in Clerk Elements' XState logic were applied to make sure that during a sign-in/sign-up attempt the state is properly maintained. For example, if you visit an already completed attempt (some step of that flow) it now properly keeps track of that state.

Minor Changes

• Updates related to experimental Google One Tap support (#3250) by @panteliselef

  • By default we are returning back to the location where the flow started.
    To accomplish that internally we will use the redirect_url query parameter to build the url.

  <__experimental_GoogleOneTap />
  

  • In the above example if there is a SIGN_UP_FORCE_REDIRECT_URL or SIGN_IN_FORCE_REDIRECT_URL set then the developer would need to pass new values as props like this

  <__experimental_GoogleOneTap
    signInForceRedirectUrl=''
    signUpForceRedirectUrl=''
  />
  

  • Let the developer configure the experience they want to offer. (All these values are true by default)

  <__experimental_GoogleOneTap
    cancelOnTapOutside={false}
    itpSupport={false}
    fedCmSupport={false}
  />
  

  • Moved authenticateWithGoogleOneTap to Clerk singleton

  Clerk.__experimental_authenticateWithGoogleOneTap;
  

  • Created the handleGoogleOneTapCallback in Clerk singleton

  Clerk.__experimental_handleGoogleOneTapCallback;
  

• Introduce new client_mismatch verification status for email link sign-in and sign-up. This error (and its message) will be shown if a verification link was opened in another device/browser from which the user initiated the sign-in/sign-up attempt. This functionality needs to be enabled in the Clerk dashboard. (#3367) by @mzhong9723

Patch Changes

• Improve logging for CAPTCHA script loading errors (#3374) by @anagstef

• Respect the signInForceRedirectUrl, signInFallbackRedirectUrl, signUpForceRedirectUrl and signUpFallbackRedirectUrl props passed to SignInButton, SignUpButton and the low-level window.Clerk.buildSignInUrl & window.Clerk.buildSignUpUrl methods. These props allow you to control the redirect behavior of the SignIn and SignUp components. For more information, refer to the Custom Redirects guide. (#3361) by @nikosdouvlis

• Updated dependencies [6f61130e3, 94197710a, b27ca8366, 201b28d37, b27ca8366]:

  • @clerk/[email protected]
  • @clerk/[email protected]
  • @clerk/[email protected]

Patch Changes

• Remove Origin from API mutation request headers via onInstalled listener. (#3363) by @tmilewski

• Revert: Remove Origin from API mutation request headers via onInstalled listener. (#3375) by @tmilewski

• Updated dependencies [94197710a, 34befeebc, b27ca8366, bcbb2c9ef]:

  • @clerk/[email protected]
  • @clerk/[email protected]
  • @clerk/[email protected]