Skip to content

ci(repo): Version packages - #9931

Merged
wobsoriano merged 1 commit into
mainfrom
changeset-release/main
Sep 25, 2026
Merged

wobsoriano merged 1 commit into
mainfrom
changeset-release/main

Conversation

@clerk-cookie

@clerk-cookie clerk-cookie commented Sep 24, 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/localizations@4.20.0

Minor Changes

  • <SignIn /> and <SignUp /> show a dedicated screen when a request is blocked, with a reference the user can quote to support. (#9600) by @zourzouvillys

    action_blocked errors now expose traceId, title, description, linkUrl, linkText, kind and data on meta.

Patch Changes

  • Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider. (#9619) by @zourzouvillys

    If you use the prebuilt <SignIn /> component, there is nothing to do. If you have Clerk Protect enabled and call signIn.authenticateWithRedirect() or signIn.authenticateWithPopup() from a custom sign-in flow, catch a ClerkRuntimeError with code protect_check_required and show the verification challenge, to avoid a stalled sign-in.

    That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated: signIn.protectCheck is set, or its status is needs_protect_check. For enterprise SSO, run the challenge and then call authenticateWithRedirect() again with continueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown.

  • Updated dependencies [645a532, 84ee588, 4e538ac]:

    • @clerk/shared@4.36.0

@clerk/shared@4.36.0

Minor Changes

  • <SignIn /> and <SignUp /> show a dedicated screen when a request is blocked, with a reference the user can quote to support. (#9600) by @zourzouvillys

    action_blocked errors now expose traceId, title, description, linkUrl, linkText, kind and data on meta.

Patch Changes

  • Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider. (#9619) by @zourzouvillys

    If you use the prebuilt <SignIn /> component, there is nothing to do. If you have Clerk Protect enabled and call signIn.authenticateWithRedirect() or signIn.authenticateWithPopup() from a custom sign-in flow, catch a ClerkRuntimeError with code protect_check_required and show the verification challenge, to avoid a stalled sign-in.

    That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated: signIn.protectCheck is set, or its status is needs_protect_check. For enterprise SSO, run the challenge and then call authenticateWithRedirect() again with continueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown.

  • Run a sign-up's verification challenge before handing off to an enterprise connection, matching the order used elsewhere in the flow. (#9622) by @zourzouvillys

@clerk/ui@1.36.0

Minor Changes

  • <SignIn /> and <SignUp /> show a dedicated screen when a request is blocked, with a reference the user can quote to support. (#9600) by @zourzouvillys

    action_blocked errors now expose traceId, title, description, linkUrl, linkText, kind and data on meta.

Patch Changes

  • Clear the invitation ticket from the URL when a sign-in completes on a verification challenge. (#9621) by @zourzouvillys

  • Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider. (#9619) by @zourzouvillys

    If you use the prebuilt <SignIn /> component, there is nothing to do. If you have Clerk Protect enabled and call signIn.authenticateWithRedirect() or signIn.authenticateWithPopup() from a custom sign-in flow, catch a ClerkRuntimeError with code protect_check_required and show the verification challenge, to avoid a stalled sign-in.

    That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated: signIn.protectCheck is set, or its status is needs_protect_check. For enterprise SSO, run the challenge and then call authenticateWithRedirect() again with continueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown.

  • Fix the verification challenge card spinning indefinitely when continuing the sign-in after a completed challenge fails. The error is now shown, and "Try again" retries the continuation. (#9620) by @zourzouvillys

  • Fix sign-ins that use an enterprise connection stranding on "Use another method" after a verification challenge, instead of continuing to the identity provider. (#9620) by @zourzouvillys

  • Updated dependencies [645a532, 84ee588, 4e538ac]:

    • @clerk/localizations@4.20.0
    • @clerk/shared@4.36.0

@clerk/astro@4.1.6

Patch Changes

@clerk/backend@3.20.1

Patch Changes

@clerk/chrome-extension@3.1.87

Patch Changes

@clerk/clerk-js@6.34.1

Patch Changes

  • Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider. (#9619) by @zourzouvillys

    If you use the prebuilt <SignIn /> component, there is nothing to do. If you have Clerk Protect enabled and call signIn.authenticateWithRedirect() or signIn.authenticateWithPopup() from a custom sign-in flow, catch a ClerkRuntimeError with code protect_check_required and show the verification challenge, to avoid a stalled sign-in.

    That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated: signIn.protectCheck is set, or its status is needs_protect_check. For enterprise SSO, run the challenge and then call authenticateWithRedirect() again with continueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown.

  • Updated dependencies [645a532, 84ee588, 4e538ac]:

    • @clerk/shared@4.36.0

@clerk/electron@0.0.47

Patch Changes

  • Updated dependencies [645a532, 84ee588, 4e538ac]:
    • @clerk/shared@4.36.0
    • @clerk/clerk-js@6.34.1
    • @clerk/react@6.17.2

@clerk/expo@4.7.1

Patch Changes

  • Updated dependencies [645a532, 84ee588, 4e538ac]:
    • @clerk/shared@4.36.0
    • @clerk/clerk-js@6.34.1
    • @clerk/react@6.17.2

@clerk/expo-passkeys@2.0.23

Patch Changes

@clerk/express@2.1.72

Patch Changes

@clerk/fastify@3.1.82

Patch Changes

@clerk/hono@0.1.82

Patch Changes

@clerk/mosaic@0.1.2

Patch Changes

@clerk/nextjs@7.9.7

Patch Changes

  • Updated dependencies [645a532, 84ee588, 4e538ac]:
    • @clerk/shared@4.36.0
    • @clerk/react@6.17.2
    • @clerk/backend@3.20.1

@clerk/nuxt@3.1.6

Patch Changes

  • Updated dependencies [645a532, 84ee588, 4e538ac]:
    • @clerk/shared@4.36.0
    • @clerk/backend@3.20.1
    • @clerk/vue@2.5.6

@clerk/react@6.17.2

Patch Changes

@clerk/react-router@3.6.27

Patch Changes

  • Updated dependencies [645a532, 84ee588, 4e538ac]:
    • @clerk/shared@4.36.0
    • @clerk/react@6.17.2
    • @clerk/backend@3.20.1

@clerk/tanstack-react-start@1.6.1

Patch Changes

  • Updated dependencies [645a532, 84ee588, 4e538ac]:
    • @clerk/shared@4.36.0
    • @clerk/react@6.17.2
    • @clerk/backend@3.20.1

@clerk/testing@2.2.39

Patch Changes

@clerk/vue@2.5.6

Patch Changes

@clerk/msw@0.0.73

Patch Changes

@clerk/swingset@0.0.50

Patch Changes

  • Updated dependencies [645a532, 84ee588, 4e538ac]:
    • @clerk/shared@4.36.0
    • @clerk/mosaic@0.1.2
    • @clerk/nextjs@7.9.7

@vercel

vercel Bot commented Sep 24, 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 Sep 25, 2026 12:05am UTC
swingset Ready Ready Preview Sep 25, 2026 12:05am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Sep 24, 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

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Advanced

Run ID: fa9bfc79-a3c6-43f3-b0b3-f96f25b12b11

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

Comment @coderabbitai help to get the list of available commands.

@pkg-pr-new

pkg-pr-new Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

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

@clerk/electron-passkeys

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

@clerk/eslint-plugin

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

@clerk/expo

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

@clerk/expo-google-signin

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/mosaic

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 35337cc

@github-actions

github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

API Changes Report

Generated by Break Check on 2026-09-25T00:06:10.394Z

Summary

Metric Count
Packages analyzed 19
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 35337cc.

@wobsoriano
wobsoriano merged commit 750e7fc into main Sep 25, 2026
84 of 85 checks passed
@wobsoriano
wobsoriano deleted the changeset-release/main branch September 25, 2026 00:47

This branch was successfully deployed

2 active deployments
Preview – swingset — 35337cca Deployed Sep 25, 2026 by vercel[bot]
Preview – clerk-js-sandbox — 35337cca Deployed Sep 25, 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