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 #4247

Merged
merged 1 commit into from
Oct 2, 2024
Merged

ci(repo): Version packages #4247

merged 1 commit into from
Oct 2, 2024

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented Sep 30, 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

  • Drop the experimental mounted variant of UserVerification. (#4266) by @panteliselef

    Removes:

    • <__experimental_UserVerification/>
    • __experimental_mountUserVerification()
    • __experimental_unmountUserVerification()

  • Experimental Feature: <UserProfile/> allows users to update their information. Mostly of this information is considered sensitive data. (#4127) by @panteliselef

    We want to ensure that only the users themselves can alter any sensitive data.

    To increase security we are now, require users to re-verify their credentials when they are about to perform these actions:

    Operation Reverification Strategy Timeframe
    Update account (first/last name) ❌
    Update username ✅ Strongest available 10m
    Delete account ✅ Strongest available 10m
    Create/Remove profile image ❌
    Update password ✅ Strongest available 10m
    Remove password ❌
    Revoke session ✅ Strongest available 10m
    Create identification ✅ Strongest available 10m
    Remove identification ✅ Strongest available 10m
    Change primary identification ✅ Strongest available 10m
    Update Passkey name ❌
    Enable MFA (TOTP, Phone number) ✅ Strongest available 10m
    Disable MFA (TOΤP, Phone number) ✅ Strongest available 10m
    Create/Regenerate Backup Codes ✅ Strongest available 10m
    Connect External Account ✅ Strongest available 10m
    Re-authorize External Account ❌
    Remove External Account ✅ Strongest available 10m
    Leave organization ❌

  • We recently shipped an experimental feature to persist the Clerk client (under persistClient flag) as an opt-in. This allows for matching a user's device with a client. We want to test this behavior with more users, so we're making it opt-out as the next step. After more successful testing we'll remove the experimental flag and enable it by default. (#4250) by @panteliselef

    If you're encountering issues, please open an issue. You can disable this new behavior like so:

    // React
<ClerkProvider experimental={{ persistClient: false }} />;

// Vanilla JS
await clerk.load({ experimental: { persistClient: false } });

Patch Changes

@clerk/[email protected]

Minor Changes

Patch Changes

@clerk/[email protected]

Minor Changes

  • Drop the experimental mounted variant of UserVerification. (#4266) by @panteliselef

    Removes:

    • <__experimental_UserVerification/>
    • __experimental_mountUserVerification()
    • __experimental_unmountUserVerification()

Patch Changes

@clerk/[email protected]

Minor Changes

  • Drop the experimental mounted variant of UserVerification. (#4266) by @panteliselef

    Removes:

    • <__experimental_UserVerification/>
    • __experimental_mountUserVerification()
    • __experimental_unmountUserVerification()

Patch Changes

@clerk/[email protected]

Minor Changes

  • Drop the experimental mounted variant of UserVerification. (#4266) by @panteliselef

    Removes:

    • <__experimental_UserVerification/>
    • __experimental_mountUserVerification()
    • __experimental_unmountUserVerification()

  • Experimental Feature: <UserProfile/> allows users to update their information. Mostly of this information is considered sensitive data. (#4127) by @panteliselef

    We want to ensure that only the users themselves can alter any sensitive data.

    To increase security we are now, require users to re-verify their credentials when they are about to perform these actions:

    Operation Reverification Strategy Timeframe
    Update account (first/last name) ❌
    Update username ✅ Strongest available 10m
    Delete account ✅ Strongest available 10m
    Create/Remove profile image ❌
    Update password ✅ Strongest available 10m
    Remove password ❌
    Revoke session ✅ Strongest available 10m
    Create identification ✅ Strongest available 10m
    Remove identification ✅ Strongest available 10m
    Change primary identification ✅ Strongest available 10m
    Update Passkey name ❌
    Enable MFA (TOTP, Phone number) ✅ Strongest available 10m
    Disable MFA (TOΤP, Phone number) ✅ Strongest available 10m
    Create/Regenerate Backup Codes ✅ Strongest available 10m
    Connect External Account ✅ Strongest available 10m
    Re-authorize External Account ❌
    Remove External Account ✅ Strongest available 10m
    Leave organization ❌

@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 9 times, most recently from 723a5bb to dd91239 Compare October 1, 2024 14:43
@nikosdouvlis nikosdouvlis reopened this Oct 2, 2024
@nikosdouvlis nikosdouvlis merged commit 2e369ee into main Oct 2, 2024
21 checks passed
@nikosdouvlis nikosdouvlis deleted the changeset-release/main branch October 2, 2024 12:01
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 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.
2 participants
@clerk-cookie @nikosdouvlis