javascript

Patch Changes

• Fix race condition on updating ClerkProvider props before ClerkJS has loaded (#3655) by @anagstef

Patch Changes

• Updated dependencies [427fcdeaa]:
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [427fcdeaa]:
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [427fcdeaa]:
  • @clerk/[email protected]

Patch Changes

• Updated dependencies [427fcdeaa]:
  • @clerk/[email protected]

Patch Changes

• Ensure client cookie URLs resolve appropriately (#3658) by @tmilewski

• Updated dependencies [427fcdeaa]:

  • @clerk/[email protected]

Patch Changes

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

Patch Changes

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

Minor Changes

• Add backup_code verification strategy (#3627) by @tmilewski

  <SignIn.Step name='choose-strategy'>
    <SignIn.SupportedStrategy name='backup_code'>Use a backup code</SignIn.SupportedStrategy>
  <SignIn.Step>
  

  <SignIn.Step name='verifications'>
    <SignIn.Strategy name='backup_code'>
      <Clerk.Field name="backup_code">
        <Clerk.Label>Code:</Clerk.Label>
        <Clerk.Input />
        <Clerk.FieldError />
      </Clerk.Field>
  
      <Clerk.Action submit>Continue</Clerk.Action>
    </SignIn.Strategy>
  <SignIn.Step>
  

Patch Changes

• Addresses the issue where sign-in factors were not properly falling back to empty arrays. (#3647) by @LauraBeatris

• Refactors sign-up loading logic to be in-line with sign-in (#3648) by @tmilewski

• Ensure Sign Up resending resets upon being triggered (#3652) by @tmilewski

• Fixes persistent loading states within the forgot-password step (#3648) by @tmilewski

• Fix Sign In forgot-password step not rendering (#3653) by @tmilewski

Minor Changes

• Introduces dynamic keys from clerkMiddleware, allowing access by server-side helpers like auth. Keys such as signUpUrl, signInUrl, publishableKey and secretKey are securely encrypted using AES algorithm. (#3525) by @LauraBeatris

  • When providing secretKey, CLERK_ENCRYPTION_KEY is required as the encryption key. If secretKey is not provided, CLERK_SECRET_KEY is used by default.
  • clerkClient from @clerk/nextjs should now be called as a function, and its singleton form is deprecated. This change allows the Clerk backend client to read keys from the current request, which is necessary to support dynamic keys.

  For more information, refer to the documentation: https://clerk.com/docs/references/nextjs/clerk-middleware#dynamic-keys

Patch Changes

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

Minor Changes

• Add support for Remix SPA Mode (#3580) by @anagstef

Patch Changes

• Fix issues caused by modifying duplex property on Request when it was already defined (#3645) by @octoper

• Updated dependencies [f1847b70b]:

  • @clerk/[email protected]

Minor Changes

• Introduces dynamic keys from clerkMiddleware, allowing access by server-side helpers like auth. Keys such as signUpUrl, signInUrl, publishableKey and secretKey are securely encrypted using AES algorithm. (#3525) by @LauraBeatris

  • When providing secretKey, CLERK_ENCRYPTION_KEY is required as the encryption key. If secretKey is not provided, CLERK_SECRET_KEY is used by default.
  • clerkClient from @clerk/nextjs should now be called as a function, and its singleton form is deprecated. This change allows the Clerk backend client to read keys from the current request, which is necessary to support dynamic keys.

  For more information, refer to the documentation: https://clerk.com/docs/references/nextjs/clerk-middleware#dynamic-keys

Patch Changes

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

Patch Changes

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

Patch Changes

• Add a development-only warning for cases when a user renders a <Strategy> component that isn't activated for their Clerk instance. As this can be intended behavior (e.g. build out a full example and let user enable/disable stuff solely in the dashboard) the warning can safely be ignored if necessary. (#3609) by @LekoArts

Patch Changes

• Correctly use updated protocol verification in all code paths (#3605) by @LekoArts

• Updated dependencies [72888323b]:

  • @clerk/[email protected]

Patch Changes

• Updated dependencies [2bef41ab0]:
  • @clerk/[email protected]

Patch Changes

• Add Italian localizations (#3608) by @mazzasaverio

Minor Changes

• Improve <FieldState> and re-organize some data attributes related to validity states. These changes might be breaking changes for you. (#3594) by @LekoArts

  Overview of changes:

  • <form> no longer has data-valid and data-invalid attributes. If there are global errors (same heuristics as <GlobalError>) then a data-global-error attribute will be present.
  • Fixed a bug where <Field> could contain data-valid and data-invalid at the same time.
  • The field state (accessible through e.g. <FieldState>) now also incorporates the field's ValidityState into its output. If the ValidityState is invalid, the field state will be an error. You can access this information in three places:
    1. <FieldState>
    2. data-state attribute on <Input>
    3. <Field>{(state) => <p>Field's state is {state}</p>}</Field>

Patch Changes

• Fix Sign In & Sign Up root fallbacks not rendering as expected (#3601) by @tmilewski

• Update all Radix dependencies to their June 19, 2024 release (#3606) by @LekoArts