Skip to content

ci(repo): Version packages - #4504

Merged
alexcarpenter merged 1 commit into
mainfrom
changeset-release/main
Nov 8, 2024
Merged

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

Conversation

@clerk-cookie

@clerk-cookie clerk-cookie commented Nov 6, 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.16.0

Minor Changes

  • Send API version through request headers. (#4458) by @jacekradko

  • Introduce experimental verification helpers exported from @clerk/backend/internal (#4480) by @panteliselef

    • __experimental_reverificationMismatch
    • __experimental_reverificationMismatchResponse

Patch Changes

@clerk/clerk-js@5.32.0

Minor Changes

  • Introduce experimental support for passkeys in Expo (iOS, Android, and Web). (#4352) by @AlexNti

    To use passkeys in Expo projects, pass the __experimental_passkeys object, which can be imported from @clerk/clerk-expo/passkeys, to the ClerkProvider component:

    import { ClerkProvider } from '@clerk/clerk-expo';
    import { passkeys } from '@clerk/clerk-expo/passkeys';
    
    <ClerkProvider __experimental_passkeys={passkeys}>{/* Your app here */}</ClerkProvider>;

    The API for using passkeys in Expo projects is the same as the one used in web apps:

    // passkey creation
    const { user } = useUser();
    
    const handleCreatePasskey = async () => {
      if (!user) return;
      try {
        return await user.createPasskey();
      } catch (e: any) {
        // handle error
      }
    };
    
    // passkey authentication
    const { signIn, setActive } = useSignIn();
    
    const handlePasskeySignIn = async () => {
      try {
        const signInResponse = await signIn.authenticateWithPasskey();
        await setActive({ session: signInResponse.createdSessionId });
      } catch (err: any) {
        //handle error
      }
    };
  • The Legal consent feature is now stable. (#4487) by @octoper

    Removed the __experimental_ preffix.

  • Now sending the Frontend API version through query string params (#4457) by @jacekradko

Patch Changes

@clerk/elements@0.19.0

Minor Changes

  • Introduce support for <SignIn.Captcha /> and <SignIn.Step name='sso-callback'>. This allows rendering of a CAPTCHA widget when a sign in attempt is transferred to a sign up attempt. (#4523) by @BRKalow

  • The Legal consent feature is now stable. (#4487) by @octoper

    Removed the __experimental_ preffix.

Patch Changes

@clerk/clerk-expo@2.3.0

Minor Changes

  • Introduce experimental support for passkeys in Expo (iOS, Android, and Web). (#4352) by @AlexNti

    To use passkeys in Expo projects, pass the __experimental_passkeys object, which can be imported from @clerk/clerk-expo/passkeys, to the ClerkProvider component:

    import { ClerkProvider } from '@clerk/clerk-expo';
    import { passkeys } from '@clerk/clerk-expo/passkeys';
    
    <ClerkProvider __experimental_passkeys={passkeys}>{/* Your app here */}</ClerkProvider>;

    The API for using passkeys in Expo projects is the same as the one used in web apps:

    // passkey creation
    const { user } = useUser();
    
    const handleCreatePasskey = async () => {
      if (!user) return;
      try {
        return await user.createPasskey();
      } catch (e: any) {
        // handle error
      }
    };
    
    // passkey authentication
    const { signIn, setActive } = useSignIn();
    
    const handlePasskeySignIn = async () => {
      try {
        const signInResponse = await signIn.authenticateWithPasskey();
        await setActive({ session: signInResponse.createdSessionId });
      } catch (err: any) {
        //handle error
      }
    };

Patch Changes

@clerk/localizations@3.6.0

Minor Changes

  • The Legal consent feature is now stable. (#4487) by @octoper

    Removed the __experimental_ preffix.

Patch Changes

@clerk/nextjs@6.3.0

Minor Changes

  • Introduce experimental verification helpers exported from @clerk/nextjs/server (#4480) by @panteliselef

    • __experimental_reverificationMismatch
    • __experimental_reverificationMismatchResponse

Patch Changes

@clerk/shared@2.12.0

Minor Changes

  • Introduce experimental support for passkeys in Expo (iOS, Android, and Web). (#4352) by @AlexNti

    To use passkeys in Expo projects, pass the __experimental_passkeys object, which can be imported from @clerk/clerk-expo/passkeys, to the ClerkProvider component:

    import { ClerkProvider } from '@clerk/clerk-expo';
    import { passkeys } from '@clerk/clerk-expo/passkeys';
    
    <ClerkProvider __experimental_passkeys={passkeys}>{/* Your app here */}</ClerkProvider>;

    The API for using passkeys in Expo projects is the same as the one used in web apps:

    // passkey creation
    const { user } = useUser();
    
    const handleCreatePasskey = async () => {
      if (!user) return;
      try {
        return await user.createPasskey();
      } catch (e: any) {
        // handle error
      }
    };
    
    // passkey authentication
    const { signIn, setActive } = useSignIn();
    
    const handlePasskeySignIn = async () => {
      try {
        const signInResponse = await signIn.authenticateWithPasskey();
        await setActive({ session: signInResponse.createdSessionId });
      } catch (err: any) {
        //handle error
      }
    };

Patch Changes

@clerk/types@4.31.0

Minor Changes

  • Introduce experimental support for passkeys in Expo (iOS, Android, and Web). (#4352) by @AlexNti

    To use passkeys in Expo projects, pass the __experimental_passkeys object, which can be imported from @clerk/clerk-expo/passkeys, to the ClerkProvider component:

    import { ClerkProvider } from '@clerk/clerk-expo';
    import { passkeys } from '@clerk/clerk-expo/passkeys';
    
    <ClerkProvider __experimental_passkeys={passkeys}>{/* Your app here */}</ClerkProvider>;

    The API for using passkeys in Expo projects is the same as the one used in web apps:

    // passkey creation
    const { user } = useUser();
    
    const handleCreatePasskey = async () => {
      if (!user) return;
      try {
        return await user.createPasskey();
      } catch (e: any) {
        // handle error
      }
    };
    
    // passkey authentication
    const { signIn, setActive } = useSignIn();
    
    const handlePasskeySignIn = async () => {
      try {
        const signInResponse = await signIn.authenticateWithPasskey();
        await setActive({ session: signInResponse.createdSessionId });
      } catch (err: any) {
        //handle error
      }
    };
  • The Legal consent feature is now stable. (#4487) by @octoper

    Removed the __experimental_ preffix.

Patch Changes

  • Fixes issues in ClerkRouter that were causing inaccurate pathnames within Elements flows. Also fixes a dependency issue where @clerk/elements was pulling in the wrong version of @clerk/shared. (#4513) by @alexcarpenter

  • Add afterJoinWaitlistUrl to DisplayConfig resource (#4524) by @nikospapcom

@clerk/astro@1.4.8

Patch Changes

@clerk/chrome-extension@1.3.31

Patch Changes

@clerk/expo-passkeys@0.0.2

Patch Changes

  • Introduce experimental support for passkeys in Expo (iOS, Android, and Web). (#4352) by @AlexNti

    To use passkeys in Expo projects, pass the __experimental_passkeys object, which can be imported from @clerk/clerk-expo/passkeys, to the ClerkProvider component:

    import { ClerkProvider } from '@clerk/clerk-expo';
    import { passkeys } from '@clerk/clerk-expo/passkeys';
    
    <ClerkProvider __experimental_passkeys={passkeys}>{/* Your app here */}</ClerkProvider>;

    The API for using passkeys in Expo projects is the same as the one used in web apps:

    // passkey creation
    const { user } = useUser();
    
    const handleCreatePasskey = async () => {
      if (!user) return;
      try {
        return await user.createPasskey();
      } catch (e: any) {
        // handle error
      }
    };
    
    // passkey authentication
    const { signIn, setActive } = useSignIn();
    
    const handlePasskeySignIn = async () => {
      try {
        const signInResponse = await signIn.authenticateWithPasskey();
        await setActive({ session: signInResponse.createdSessionId });
      } catch (err: any) {
        //handle error
      }
    };
  • Updated dependencies [5a21de1f46df3642828dc27e4862263c9858da2b, f7472e22877f62fc7f3c8d3efe409ff2276fb4a3, e199037b8f484abdeeb9fc24455a1b4b8c31c8dd, 886e294a8d8c54b39cd5bda88d46b89eace3861e, 0e443ad7c76643420b50e5b169193e03f6ef79f9, cc24c8145f1eea7fb91550f2c3e0bac3993e4320]:

    • @clerk/shared@2.12.0
    • @clerk/types@4.31.0

@clerk/express@1.3.10

Patch Changes

@clerk/fastify@2.0.12

Patch Changes

@clerk/clerk-react@5.15.2

Patch Changes

@clerk/remix@4.2.48

Patch Changes

@clerk/clerk-sdk-node@5.0.61

Patch Changes

@clerk/tanstack-start@0.4.24

Patch Changes

@clerk/testing@1.3.22

Patch Changes

@clerk/themes@2.1.42

Patch Changes

@clerk/ui@0.1.17

Patch Changes

@clerk/vue@0.0.1

Patch Changes

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 5 times, most recently from 3627a2e to 0b813f1 Compare November 8, 2024 16:22
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0b813f1 to c7e7528 Compare November 8, 2024 17:20
@octoper octoper closed this Nov 8, 2024
@octoper octoper reopened this Nov 8, 2024
@alexcarpenter
alexcarpenter self-requested a review November 8, 2024 20:24
@alexcarpenter
alexcarpenter merged commit f2cb38e into main Nov 8, 2024
@alexcarpenter
alexcarpenter deleted the changeset-release/main branch November 8, 2024 20:24
wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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.

4 participants