Skip to content

Version Packages#3370

Merged
nikosdouvlis merged 1 commit intomainfrom
changeset-release/main
May 14, 2024
Merged

Version Packages#3370
nikosdouvlis merged 1 commit intomainfrom
changeset-release/main

Conversation

@clerk-cookie
Copy link
Copy Markdown
Collaborator

@clerk-cookie clerk-cookie commented May 13, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@clerk/clerk-js@5.3.0

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/localizations@2.4.0
    • @clerk/types@4.3.0
    • @clerk/shared@2.1.0

@clerk/localizations@2.4.0

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

@clerk/shared@2.1.0

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

@clerk/types@4.3.0

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

@clerk/backend@1.1.4

Patch Changes

  • Updated dependencies [b27ca8366]:
    • @clerk/shared@2.1.0

@clerk/chrome-extension@1.0.9

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/clerk-js@5.3.0
    • @clerk/shared@2.1.0
    • @clerk/clerk-react@5.0.5

@clerk/elements@0.4.1

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.

@clerk/clerk-expo@1.1.1

Patch Changes

@clerk/express@0.0.7

Patch Changes

  • Updated dependencies [b27ca8366]:
    • @clerk/shared@2.1.0
    • @clerk/backend@1.1.4

@clerk/fastify@1.0.6

Patch Changes

  • Updated dependencies [94197710a, b27ca8366]:
    • @clerk/types@4.3.0
    • @clerk/shared@2.1.0
    • @clerk/backend@1.1.4

@clerk/nextjs@5.0.9

Patch Changes

  • Updated dependencies [b27ca8366, bcbb2c9ef]:
    • @clerk/shared@2.1.0
    • @clerk/clerk-react@5.0.5
    • @clerk/backend@1.1.4

@clerk/clerk-react@5.0.5

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/types@4.3.0
    • @clerk/shared@2.1.0

@clerk/remix@4.0.7

Patch Changes

  • Updated dependencies [b27ca8366, bcbb2c9ef]:
    • @clerk/shared@2.1.0
    • @clerk/clerk-react@5.0.5
    • @clerk/backend@1.1.4

@clerk/clerk-sdk-node@5.0.6

Patch Changes

  • Updated dependencies [b27ca8366]:
    • @clerk/shared@2.1.0
    • @clerk/backend@1.1.4

@clerk/testing@1.0.4

Patch Changes

@clerk/themes@2.1.4

Patch Changes

@github-actions github-actions Bot force-pushed the changeset-release/main branch 7 times, most recently from 348cff1 to 0dff78a Compare May 14, 2024 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants