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

ci(repo): Version packages #4504

Merged
merged 1 commit into from
Nov 8, 2024
Merged

ci(repo): Version packages #4504

merged 1 commit into from
Nov 8, 2024

Conversation

clerk-cookie
Copy link
Collaborator

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

  • 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/[email protected]

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/[email protected]

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/[email protected]

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/[email protected]

Minor Changes

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

    Removed the __experimental_ preffix.

Patch Changes

@clerk/[email protected]

Minor Changes

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

    • __experimental_reverificationMismatch
    • __experimental_reverificationMismatchResponse

Patch Changes

@clerk/[email protected]

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/[email protected]

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/[email protected]

Patch Changes

@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

@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

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch 2 times, most recently from 2c299b0 to fa943a6 Compare November 6, 2024 16:55
@nikosdouvlis nikosdouvlis reopened this Nov 6, 2024
@github-actions github-actions bot force-pushed the changeset-release/main branch 10 times, most recently from 66ede19 to e374f6c Compare November 8, 2024 03:26
@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
25 checks passed
@alexcarpenter alexcarpenter deleted the changeset-release/main branch November 8, 2024 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alexcarpenter alexcarpenter alexcarpenter approved these changes

Assignees
No one assigned
Labels
backend chrome-extension clerk-js elements expo express fastify localizations nextjs react remix sdk-node tanstack testing themes types
Projects
None yet
Milestone
No milestone
Development

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