Skip to content

ci(repo): Version packages - #3400

Merged
nikosdouvlis merged 1 commit into
mainfrom
changeset-release/main
May 21, 2024
Merged

ci(repo): Version packages#3400
nikosdouvlis merged 1 commit into
mainfrom
changeset-release/main

Conversation

@clerk-cookie

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

Copy link
Copy Markdown
Collaborator

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/backend@1.2.0

Minor Changes

  • Consume and expose the 'saml_accounts' property of the user resource (#3405) by @chanioxaris

Patch Changes

  • Updated dependencies [456b06849]:
    • @clerk/shared@2.2.0

@clerk/clerk-js@5.5.0

Minor Changes

  • Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef

    React component

    • <GoogleOneTap/>

    Customize the UX of the prompt

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

    Use the component from with Vanilla JS

    • Clerk.openGoogleOneTap(props: GoogleOneTapProps)
    • Clerk.closeGoogleOneTap()

    Low level APIs for custom flows

    • await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
    • await Clerk.handleGoogleOneTapCallback()

    We recommend using this two methods together in order and let Clerk to perform the correct redirections.

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        await Clerk.handleGoogleOneTapCallback(signInOrUp, {
          signInForceRedirectUrl: window.location.href,
        });
      },
    });

    In case you want to handle the redirection and session management yourself you can do so like this

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        if (signInOrUp.status === 'complete') {
          await Clerk.setActive({
            session: signInOrUp.createdSessionId,
          });
        }
      },
    });

Patch Changes

  • A bug was fixed to not override the existing sign-up state on the OAuth callback. (#3401) by @LauraBeatris

    When continuing a sign-up flow with social connections, @clerk/clerk-js was creating a new SignUpResource object, instead of patching the existing one.

    This was affecting Web3 sign-up flows, since the wallet ID was being overridden on the browser redirect.

  • Updated dependencies [d6a9b3f5d, 456b06849]:

    • @clerk/types@4.5.0
    • @clerk/shared@2.2.0

@clerk/nextjs@5.1.0

Minor Changes

  • Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef

    React component

    • <GoogleOneTap/>

    Customize the UX of the prompt

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

    Use the component from with Vanilla JS

    • Clerk.openGoogleOneTap(props: GoogleOneTapProps)
    • Clerk.closeGoogleOneTap()

    Low level APIs for custom flows

    • await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
    • await Clerk.handleGoogleOneTapCallback()

    We recommend using this two methods together in order and let Clerk to perform the correct redirections.

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        await Clerk.handleGoogleOneTapCallback(signInOrUp, {
          signInForceRedirectUrl: window.location.href,
        });
      },
    });

    In case you want to handle the redirection and session management yourself you can do so like this

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        if (signInOrUp.status === 'complete') {
          await Clerk.setActive({
            session: signInOrUp.createdSessionId,
          });
        }
      },
    });

Patch Changes

@clerk/clerk-react@5.2.0

Minor Changes

  • Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef

    React component

    • <GoogleOneTap/>

    Customize the UX of the prompt

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

    Use the component from with Vanilla JS

    • Clerk.openGoogleOneTap(props: GoogleOneTapProps)
    • Clerk.closeGoogleOneTap()

    Low level APIs for custom flows

    • await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
    • await Clerk.handleGoogleOneTapCallback()

    We recommend using this two methods together in order and let Clerk to perform the correct redirections.

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        await Clerk.handleGoogleOneTapCallback(signInOrUp, {
          signInForceRedirectUrl: window.location.href,
        });
      },
    });

    In case you want to handle the redirection and session management yourself you can do so like this

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        if (signInOrUp.status === 'complete') {
          await Clerk.setActive({
            session: signInOrUp.createdSessionId,
          });
        }
      },
    });

Patch Changes

@clerk/shared@2.2.0

Minor Changes

@clerk/types@4.5.0

Minor Changes

  • Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef

    React component

    • <GoogleOneTap/>

    Customize the UX of the prompt

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

    Use the component from with Vanilla JS

    • Clerk.openGoogleOneTap(props: GoogleOneTapProps)
    • Clerk.closeGoogleOneTap()

    Low level APIs for custom flows

    • await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
    • await Clerk.handleGoogleOneTapCallback()

    We recommend using this two methods together in order and let Clerk to perform the correct redirections.

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        await Clerk.handleGoogleOneTapCallback(signInOrUp, {
          signInForceRedirectUrl: window.location.href,
        });
      },
    });

    In case you want to handle the redirection and session management yourself you can do so like this

    google.accounts.id.initialize({
      callback: async response => {
        const signInOrUp = await Clerk.authenticateWithGoogleOneTap({ token: response.credential });
        if (signInOrUp.status === 'complete') {
          await Clerk.setActive({
            session: signInOrUp.createdSessionId,
          });
        }
      },
    });

@clerk/chrome-extension@1.0.13

Patch Changes

@clerk/clerk-expo@1.1.5

Patch Changes

@clerk/express@0.0.9

Patch Changes

@clerk/fastify@1.0.10

Patch Changes

@clerk/remix@4.0.11

Patch Changes

@clerk/clerk-sdk-node@5.0.8

Patch Changes

@clerk/testing@1.1.3

Patch Changes

  • Add experimental console warning on Cypress setup function (#3395) by @anagstef

  • Updated dependencies [d6a9b3f5d, 456b06849]:

    • @clerk/types@4.5.0
    • @clerk/shared@2.2.0

@clerk/themes@2.1.7

Patch Changes

  • Updated dependencies [d6a9b3f5d]:
    • @clerk/types@4.5.0

@clerk/elements@0.4.6

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1fb30b7 to 9427f94 Compare May 21, 2024 19:59
@nikosdouvlis nikosdouvlis reopened this May 21, 2024
@nikosdouvlis
nikosdouvlis merged commit 7ee868c into main May 21, 2024
@nikosdouvlis
nikosdouvlis deleted the changeset-release/main branch May 21, 2024 20:23
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