search

wobsoriano / svelte-clerk

Community Clerk Svelte SDK.
Other
36 stars 4 forks source link

chore(deps): bump the clerk-dependencies group with 3 updates #90

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps the clerk-dependencies group with 3 updates: @clerk/backend, @clerk/shared and @clerk/types.

Updates @clerk/backend from 1.15.7 to 1.16.0

Release notes

Sourced from @​clerk/backend's 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

Changelog

Sourced from @​clerk/backend's changelog.

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

Commits


Updates @clerk/shared from 2.11.5 to 2.12.0

Release notes

Sourced from @​clerk/shared's releases.

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

  • Adding missing dependencies to package.json (#4522) by @​jacekradko

  • 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

  • Fixing the peerDependencies for react and react-dom (#4494) by @​jacekradko

... (truncated)

Changelog

Sourced from @​clerk/shared's changelog.

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

  • Adding missing dependencies to package.json (#4522) by @​jacekradko

  • 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

  • Fixing the peerDependencies for react and react-dom (#4494) by @​jacekradko

... (truncated)

Commits


Updates @clerk/types from 4.30.0 to 4.31.0

Release notes

Sourced from @​clerk/types's releases.

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

... (truncated)

Changelog

Sourced from @​clerk/types's changelog.

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

... (truncated)

Commits
  • f2cb38e ci(repo): Version packages (#4504)
  • cc24c81 feat(clerk-js,elements,types,localization): Make legal consent stable (#4487)
  • 0e443ad chore(clerk-js,types): Add afterJoinWaitlistUrl to DisplayConfig resource (#4...
  • f7472e2 fix(elements): Fix elements router usage (#4513)
  • e199037 feat(clerk-expo): Support expo passkeys (#4352)
  • See full diff in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions