Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Version Packages #3370

Merged
merged 1 commit into from
May 14, 2024
Merged

Version Packages #3370

merged 1 commit into from
May 14, 2024

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented May 13, 2024 •
edited
Loading

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/[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

@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

@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

@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

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@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.

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@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]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

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
@github-actions github-actions bot force-pushed the changeset-release/main branch from 0dff78a to 51a532e Compare May 14, 2024 10:54
@nikosdouvlis nikosdouvlis reopened this May 14, 2024
@nikosdouvlis nikosdouvlis merged commit ec2b683 into main May 14, 2024
10 checks passed
@nikosdouvlis nikosdouvlis deleted the changeset-release/main branch May 14, 2024 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
backend chrome-extension clerk-js elements expo express fastify gatsby localizations nextjs react remix sdk-node testing themes types
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@clerk-cookie @nikosdouvlis