Skip to content

ci(repo): Version packages - #10844

Merged
wobsoriano merged 1 commit into
mainfrom
changeset-release/main
Nov 17, 2026
Merged

wobsoriano merged 1 commit into
mainfrom
changeset-release/main

Conversation

@clerk-cookie

@clerk-cookie clerk-cookie commented Nov 16, 2026 •

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

Minor Changes

  • Add an experimental clerkClient.oauthApplications.__experimental_exchangeToken() method for performing an OAuth 2.0 Token Exchange (RFC 8693) on behalf of an OAuth application. Pass your publishable key, the application's client ID and client secret, a user's OAuth access token, and the target resource to receive a new access token for that resource, for example to call a downstream API on a user's behalf. The request goes to your instance's token endpoint, derived from the publishable key (or from proxyUrl when set), so it does not require a secret key. A proxyUrl must be an absolute HTTPS URL without a query or fragment, including for loopback hosts. Token exchange requests do not follow redirects, so credentials and tokens are never forwarded to another endpoint; a redirect response throws an OAuthTokenExchangeError with code invalid_response. (#10762) by @wyattjoh

    The method checks its inputs before making any request: resource must be an absolute URI without a fragment that uses https (or http on localhost, 127.0.0.1 or [::1]), and each scope element must be a single scope token, without spaces, ", \ or non-ASCII characters. Invalid input throws an OAuthTokenExchangeError with code invalid_request and no status. Only a 200 response with a well-formed token response counts as success; any other success status, or a response with missing or mistyped members, throws an OAuthTokenExchangeError with code invalid_response. If the token endpoint rejects the exchange, the error carries the OAuth error code in code (also available as error), errorDescription, and HTTP status. OAuthTokenExchangeError is exported from @clerk/backend/errors. Network failures from fetch are not wrapped.

Patch Changes

@clerk/clerk-js@6.44.0

Minor Changes

  • Let users whose password was found in a data breach pass reverification by resetting it. Until now the reverification modal only showed the breached-password error, so these users couldn't make any change that needs reverification, including changing that password. The modal now offers "Reset your password": the user sets a new password and enters a code sent to their email or phone, as in sign-in. Their other verification methods stay available. (#10440) by @brunol95

    From UserProfile's change password form, the modal reuses the new password the user already entered, so they only enter the code.

    session.prepareFirstFactorVerification() and session.attemptFirstFactorVerification() accept the reset_password_email_code and reset_password_phone_code strategies, so custom flows can build the same reset.

    useReverification() accepts a new passReverificationResult option. With it, the fetcher receives what the reverification did as its first argument: passwordReset holds the new password and sign out choice when the user reset their password in the modal. Custom password change flows should adopt it: after the user resets their password to reverify, retrying user.updatePassword() would fail on the old currentPassword or overwrite the password the user just set.

    const { user } = useUser();
    const updatePassword = useReverification(
      (reverification: ReverificationResult | undefined, currentUser: UserResource, params: UpdateUserPasswordParams) =>
        // A password reset during reverification already saved the new password.
        reverification?.passwordReset ? currentUser.reload() : currentUser.updatePassword(params),
      { passReverificationResult: true },
    );
    
    // In the submit handler, once `user` is loaded:
    await updatePassword(user, { newPassword, signOutOfOtherSessions: true });

Patch Changes

@clerk/localizations@4.25.0

Minor Changes

  • Add localization keys for resetting a breached or compromised password from the reverification modal: reverification.passwordPwned, reverification.passwordCompromised, reverification.resetPassword, reverification.resetPasswordAlternativeMethods and reverification.resetPasswordCode. (#10440) by @brunol95

Patch Changes

@clerk/mosaic@0.6.0

Minor Changes

Patch Changes

  • Export Avatar, Badge, Banner, Button, DataList, EmptyState, Entity, Heading, Icon, Input, Item, Skeleton, Table and Text from @clerk/mosaic/components/<name>, and the External glyph from @clerk/mosaic/icons/glyphs/external, the import paths Swingset documents. Style them with @clerk/mosaic/styles.css. (#10754) by @djgould

  • Export ActionMenu, Panel, Profile, Radio, Section and SegmentedControl from @clerk/mosaic/components/<name>, and the ArrowUpRight, Code, Plus, ShieldCheck and UserCircle glyphs from @clerk/mosaic/icons/glyphs/<name>. Style them with @clerk/mosaic/styles.css. (#10754) by @djgould

  • Updated dependencies [23ac615, 23ac615]:

    • @clerk/shared@4.46.0

@clerk/shared@4.46.0

Minor Changes

  • Let users whose password was found in a data breach pass reverification by resetting it. Until now the reverification modal only showed the breached-password error, so these users couldn't make any change that needs reverification, including changing that password. The modal now offers "Reset your password": the user sets a new password and enters a code sent to their email or phone, as in sign-in. Their other verification methods stay available. (#10440) by @brunol95

    From UserProfile's change password form, the modal reuses the new password the user already entered, so they only enter the code.

    session.prepareFirstFactorVerification() and session.attemptFirstFactorVerification() accept the reset_password_email_code and reset_password_phone_code strategies, so custom flows can build the same reset.

    useReverification() accepts a new passReverificationResult option. With it, the fetcher receives what the reverification did as its first argument: passwordReset holds the new password and sign out choice when the user reset their password in the modal. Custom password change flows should adopt it: after the user resets their password to reverify, retrying user.updatePassword() would fail on the old currentPassword or overwrite the password the user just set.

    const { user } = useUser();
    const updatePassword = useReverification(
      (reverification: ReverificationResult | undefined, currentUser: UserResource, params: UpdateUserPasswordParams) =>
        // A password reset during reverification already saved the new password.
        reverification?.passwordReset ? currentUser.reload() : currentUser.updatePassword(params),
      { passReverificationResult: true },
    );
    
    // In the submit handler, once `user` is loaded:
    await updatePassword(user, { newPassword, signOutOfOtherSessions: true });
  • Add localization keys for resetting a breached or compromised password from the reverification modal: reverification.passwordPwned, reverification.passwordCompromised, reverification.resetPassword, reverification.resetPasswordAlternativeMethods and reverification.resetPasswordCode. (#10440) by @brunol95

@clerk/ui@1.43.0

Minor Changes

  • Let users whose password was found in a data breach pass reverification by resetting it. Until now the reverification modal only showed the breached-password error, so these users couldn't make any change that needs reverification, including changing that password. The modal now offers "Reset your password": the user sets a new password and enters a code sent to their email or phone, as in sign-in. Their other verification methods stay available. (#10440) by @brunol95

    From UserProfile's change password form, the modal reuses the new password the user already entered, so they only enter the code.

    session.prepareFirstFactorVerification() and session.attemptFirstFactorVerification() accept the reset_password_email_code and reset_password_phone_code strategies, so custom flows can build the same reset.

    useReverification() accepts a new passReverificationResult option. With it, the fetcher receives what the reverification did as its first argument: passwordReset holds the new password and sign out choice when the user reset their password in the modal. Custom password change flows should adopt it: after the user resets their password to reverify, retrying user.updatePassword() would fail on the old currentPassword or overwrite the password the user just set.

    const { user } = useUser();
    const updatePassword = useReverification(
      (reverification: ReverificationResult | undefined, currentUser: UserResource, params: UpdateUserPasswordParams) =>
        // A password reset during reverification already saved the new password.
        reverification?.passwordReset ? currentUser.reload() : currentUser.updatePassword(params),
      { passReverificationResult: true },
    );
    
    // In the submit handler, once `user` is loaded:
    await updatePassword(user, { newPassword, signOutOfOtherSessions: true });

Patch Changes

  • Resume the existing session when a passkey sign-in fails with session_exists, matching the email and social sign-in paths, instead of showing "You're already signed in." (#10841) by @mikepitre

  • Updated dependencies [23ac615, 23ac615]:

    • @clerk/shared@4.46.0
    • @clerk/localizations@4.25.0

@clerk/astro@4.1.25

Patch Changes

@clerk/chrome-extension@3.1.108

Patch Changes

  • Updated dependencies [4c74f50, 23ac615, 23ac615]:
    • @clerk/ui@1.43.0
    • @clerk/shared@4.46.0
    • @clerk/clerk-js@6.44.0
    • @clerk/react@6.18.9

@clerk/electron@0.1.13

Patch Changes

  • Updated dependencies [23ac615, 23ac615]:
    • @clerk/shared@4.46.0
    • @clerk/clerk-js@6.44.0
    • @clerk/react@6.18.9

@clerk/expo@4.16.2

Patch Changes

  • Updated dependencies [23ac615, 23ac615]:
    • @clerk/shared@4.46.0
    • @clerk/clerk-js@6.44.0
    • @clerk/react@6.18.9

@clerk/expo-passkeys@2.2.2

Patch Changes

  • Fix passkey sign-in failing with passkey_authentication_failure on iOS when the passkey is in a credential manager like 1Password. The iOS module now passes the userVerification requirement to the system, so the provider asks for Face ID or a passcode before it signs. Passkey creation on iOS now always requires user verification, as it already does on Android. (#10850) by @wobsoriano

  • Updated dependencies [23ac615, 23ac615]:

    • @clerk/shared@4.46.0

@clerk/express@2.1.91

Patch Changes

@clerk/fastify@3.1.101

Patch Changes

@clerk/hono@0.1.101

Patch Changes

@clerk/nextjs@7.10.1

Patch Changes

  • Updated dependencies [11b652a, 23ac615, 23ac615]:
    • @clerk/backend@3.30.0
    • @clerk/shared@4.46.0
    • @clerk/react@6.18.9

@clerk/nuxt@3.1.25

Patch Changes

  • Updated dependencies [11b652a, 23ac615, 23ac615]:
    • @clerk/backend@3.30.0
    • @clerk/shared@4.46.0
    • @clerk/vue@2.5.22

@clerk/react@6.18.9

Patch Changes

@clerk/react-router@3.7.3

Patch Changes

  • Updated dependencies [11b652a, 23ac615, 23ac615]:
    • @clerk/backend@3.30.0
    • @clerk/shared@4.46.0
    • @clerk/react@6.18.9

@clerk/tanstack-react-start@1.7.14

Patch Changes

  • Updated dependencies [11b652a, 23ac615, 23ac615]:
    • @clerk/backend@3.30.0
    • @clerk/shared@4.46.0
    • @clerk/react@6.18.9

@clerk/testing@2.3.1

Patch Changes

@clerk/vue@2.5.22

Patch Changes

@clerk/msw@0.0.89

Patch Changes

@clerk/swingset@0.0.73

Patch Changes

@vercel

vercel Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
clerk-js-sandbox Ready Ready Preview Nov 16, 2026 11:51pm UTC
swingset Ready Ready Preview Nov 16, 2026 11:51pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords: 1

  • ci(repo): Version packages

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@blacksmith-sh

blacksmith-sh Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Matches Release versions and changelogs

Packed tarballs move from ui 1.42.6 and chrome-extension 3.1.107 to 1.42.7 and 3.1.108, the extension now requires ^1.42.7, and all four pending changesets are consumed.

Merge-base

Packed versions before

This PR 6968eae6

Packed versions after

Also checked · 1 not run

Skipped Passkey session_exists behavior · Skipped

Proof on 6968eae6 · not run: ClerkJS sandbox (The passkey fix is identical on both commits; this PR only ships it) · Did Proof get it right? Yes · No

View full Proof report · React 👎 or comment @codesmith dismiss this proof to dismiss

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

API Changes Report

Generated by Break Check on 2026-11-16T23:54:18.412Z

Summary

Metric Count
Packages analyzed 20
Packages with changes 0
🔴 Breaking changes 0
🟡 Non-breaking changes 0
🟢 Additions 0

No API Changes Detected

All packages have stable APIs with no detected changes.


Report generated by Break Check

Last ran on 875900f.

@pkg-pr-new

pkg-pr-new Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@10844

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@10844

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@10844

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@10844

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@10844

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@10844

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@10844

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@10844

@clerk/expo-biometrics

npm i https://pkg.pr.new/@clerk/expo-biometrics@10844

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@10844

@clerk/expo-native-components

npm i https://pkg.pr.new/@clerk/expo-native-components@10844

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@10844

@clerk/express

npm i https://pkg.pr.new/@clerk/express@10844

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@10844

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@10844

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@10844

@clerk/mosaic

npm i https://pkg.pr.new/@clerk/mosaic@10844

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@10844

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@10844

@clerk/react

npm i https://pkg.pr.new/@clerk/react@10844

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@10844

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@10844

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@10844

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@10844

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@10844

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@10844

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@10844

commit: 875900f

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

🟢 e2e android: 19 passed

All 19 tests in 13 files
Test Time
🟢 specs/features/custom-flow-sign-in/complete.e2e.ts · 1 passed 28.6s
🟢 useSignIn completes with the email code 28.6s
🟢 specs/features/custom-flow-sign-up/complete.e2e.ts · 1 passed 23.0s
🟢 useSignUp completes with the email code 23.0s
🟢 specs/features/native-auth-view/complete.e2e.ts · 1 passed 19.3s
🟢 signs in through AuthView with the email code 19.3s
🟢 specs/features/native-auth-view/logo.e2e.ts · 1 passed 25.1s
🟢 signs in with a password through the AuthView that has a logo, after it closed and reopened 25.1s
🟢 specs/features/native-auth-view/opens.e2e.ts · 2 passed 12.9s
🟢 the home full-screen sign-in button shows AuthView with no close button 5.4s
🟢 closing the AuthView that the home opened returns to the home 7.5s
🟢 specs/features/native-js-sync/sign-in-from-native.e2e.ts · 2 passed 48.0s
🟢 a native password sign-in reaches the JS hooks and survives a relaunch 22.4s
🟢 a second native sign-in in the same process reaches the JS hooks 25.6s
🟢 specs/features/native-js-sync/sign-out-from-native.e2e.ts · 1 passed 9.4s
🟢 signing out in the native profile signs out the JS hooks 9.4s
🟢 specs/features/native-modules/biometric-availability.e2e.ts · 1 passed 9.1s
🟢 useBiometricCredentials reports what the expo-biometrics native module found on the device 9.1s
🟢 specs/features/native-modules/google-sign-in.e2e.ts · 1 passed 12.2s
🟢 useSignInWithGoogle opens the native Google sign-in, and cancelling it ends the flow with no session 12.2s
🟢 specs/features/token-cache-persistence/relaunch.e2e.ts · 1 passed 14.9s
🟢 the token cache keeps the session across a relaunch, and a new scope starts signed out 14.9s
🟢 specs/features/update-required/update-required.e2e.ts · 3 passed 32.7s
🟢 a signed-in user on a build below the minimum sees the update screen, and is still signed in once the minimum is lowered 15.6s
🟢 a signed-out user on a build below the minimum sees the update screen 7.1s
🟢 a build at the minimum opens as usual 10.0s
🟢 specs/features/user-button-and-profile/embedded-profile.e2e.ts · 2 passed 16.0s
🟢 onHostBack closes the embedded profile after native navigation 9.3s
🟢 a custom page renders React Native content inside the embedded profile 6.7s
🟢 specs/features/user-button-and-profile/profile.e2e.ts · 2 passed 18.4s
🟢 the home UserButton opens the profile of the signed-in user 11.1s
🟢 the home sign-out button ends the session 7.3s

Tested by e2e 0.23.0 · 4m 31s · android · run artifacts

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

🟢 e2e ios: 20 passed

All 20 tests in 13 files
Test Time
🟢 specs/features/custom-flow-sign-in/complete.e2e.ts · 1 passed 25.1s
🟢 useSignIn completes with the email code 25.1s
🟢 specs/features/custom-flow-sign-up/complete.e2e.ts · 1 passed 29.5s
🟢 useSignUp completes with the email code 29.5s
🟢 specs/features/native-auth-view/complete.e2e.ts · 1 passed 24.7s
🟢 signs in through AuthView with the email code 24.7s
🟢 specs/features/native-auth-view/logo.e2e.ts · 1 passed 45.7s
🟢 signs in with a password through the AuthView that has a logo, after it closed and reopened 45.7s
🟢 specs/features/native-auth-view/opens.e2e.ts · 3 passed 18.7s
🟢 the home full-screen sign-in button shows AuthView with no close button 4.8s
🟢 closing the AuthView that the home opened returns to the home 9.5s
🟢 the close button of a full-screen AuthView returns to the home 4.5s
🟢 specs/features/native-js-sync/sign-in-from-native.e2e.ts · 2 passed 1m 32s
🟢 a native password sign-in reaches the JS hooks and survives a relaunch 37.6s
🟢 a second native sign-in in the same process reaches the JS hooks 54.8s
🟢 specs/features/native-js-sync/sign-out-from-native.e2e.ts · 1 passed 6.6s
🟢 signing out in the native profile signs out the JS hooks 6.6s
🟢 specs/features/native-modules/biometric-availability.e2e.ts · 1 passed 5.9s
🟢 useBiometricCredentials reports what the expo-biometrics native module found on the device 5.9s
🟢 specs/features/native-modules/google-sign-in.e2e.ts · 1 passed 8.5s
🟢 useSignInWithGoogle opens the native Google sign-in, and cancelling it ends the flow with no session 8.5s
🟢 specs/features/token-cache-persistence/relaunch.e2e.ts · 1 passed 9.6s
🟢 the token cache keeps the session across a relaunch, and a new scope starts signed out 9.6s
🟢 specs/features/update-required/update-required.e2e.ts · 3 passed 20.0s
🟢 a signed-in user on a build below the minimum sees the update screen, and is still signed in once the minimum is lowered 11.1s
🟢 a signed-out user on a build below the minimum sees the update screen 3.9s
🟢 a build at the minimum opens as usual 4.9s
🟢 specs/features/user-button-and-profile/embedded-profile.e2e.ts · 2 passed 13.6s
🟢 onHostBack closes the embedded profile after native navigation 7.3s
🟢 a custom page renders React Native content inside the embedded profile 6.3s
🟢 specs/features/user-button-and-profile/profile.e2e.ts · 2 passed 10.7s
🟢 the home UserButton opens the profile of the signed-in user 6.4s
🟢 the home sign-out button ends the session 4.3s

Tested by e2e 0.23.0 · 5m 11s · ios · run artifacts

@clerk-cookie
clerk-cookie force-pushed the changeset-release/main branch from 7536c6e to 147bd92 Compare November 16, 2026 20:18
@clerk-cookie
clerk-cookie force-pushed the changeset-release/main branch from 147bd92 to 22af84a Compare November 16, 2026 21:56
@clerk-cookie
clerk-cookie force-pushed the changeset-release/main branch from 22af84a to 0ec42c8 Compare November 16, 2026 22:06
@clerk-cookie
clerk-cookie force-pushed the changeset-release/main branch from 0ec42c8 to c51341a Compare November 16, 2026 22:54
@clerk-cookie
clerk-cookie force-pushed the changeset-release/main branch from c51341a to 63272bf Compare November 16, 2026 23:19
@wobsoriano
wobsoriano merged commit 6c33a72 into main Nov 17, 2026
62 checks passed
@wobsoriano
wobsoriano deleted the changeset-release/main branch November 17, 2026 00:09

This branch was successfully deployed

2 active deployments
Preview – swingset — 875900fa Deployed Nov 16, 2026 by vercel[bot]
Preview – clerk-js-sandbox — 875900fa Deployed Nov 16, 2026 by vercel[bot]
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