Skip to content

ci(repo): Version packages - #9703

Open
clerk-cookie wants to merge 1 commit into
mainfrom
changeset-release/main
Open

ci(repo): Version packages#9703
clerk-cookie wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@clerk-cookie

@clerk-cookie clerk-cookie commented Sep 10, 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/clerk-js@6.32.0

Minor Changes

  • Add the SSO fallback sign-in flow to <SignIn />, for enterprise users the instance has allowlisted to sign in with an email code when they cannot reach their identity provider. (#9685) by @mauricioabreu

    For such a user the sign-in no longer redirects straight to the identity provider. It shows the SSO action — or the connection picker, when several connections serve the address — alongside a "Can't use SSO?" link leading to the standard email code step, which carries a notice that the organization requires single sign-on and that the attempt is recorded. Users without a fallback, and instances without the feature, are unaffected.

    Custom flows can read the same factor from the new ssoFallbackFirstFactors property on the sign-in resource. The flow adds the signIn.enterpriseSSO and signIn.ssoFallback localization keys and the ssoFallback card action element id.

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0

@clerk/localizations@4.17.0

Minor Changes

  • Add the SSO fallback sign-in flow to <SignIn />, for enterprise users the instance has allowlisted to sign in with an email code when they cannot reach their identity provider. (#9685) by @mauricioabreu

    For such a user the sign-in no longer redirects straight to the identity provider. It shows the SSO action — or the connection picker, when several connections serve the address — alongside a "Can't use SSO?" link leading to the standard email code step, which carries a notice that the organization requires single sign-on and that the attempt is recorded. Users without a fallback, and instances without the feature, are unaffected.

    Custom flows can read the same factor from the new ssoFallbackFirstFactors property on the sign-in resource. The flow adds the signIn.enterpriseSSO and signIn.ssoFallback localization keys and the ssoFallback card action element id.

Patch Changes

@clerk/shared@4.32.0

Minor Changes

  • Add the SSO fallback sign-in flow to <SignIn />, for enterprise users the instance has allowlisted to sign in with an email code when they cannot reach their identity provider. (#9685) by @mauricioabreu

    For such a user the sign-in no longer redirects straight to the identity provider. It shows the SSO action — or the connection picker, when several connections serve the address — alongside a "Can't use SSO?" link leading to the standard email code step, which carries a notice that the organization requires single sign-on and that the attempt is recorded. Users without a fallback, and instances without the feature, are unaffected.

    Custom flows can read the same factor from the new ssoFallbackFirstFactors property on the sign-in resource. The flow adds the signIn.enterpriseSSO and signIn.ssoFallback localization keys and the ssoFallback card action element id.

@clerk/ui@1.33.0

Minor Changes

  • Add the SSO fallback sign-in flow to <SignIn />, for enterprise users the instance has allowlisted to sign in with an email code when they cannot reach their identity provider. (#9685) by @mauricioabreu

    For such a user the sign-in no longer redirects straight to the identity provider. It shows the SSO action — or the connection picker, when several connections serve the address — alongside a "Can't use SSO?" link leading to the standard email code step, which carries a notice that the organization requires single sign-on and that the attempt is recorded. Users without a fallback, and instances without the feature, are unaffected.

    Custom flows can read the same factor from the new ssoFallbackFirstFactors property on the sign-in resource. The flow adds the signIn.enterpriseSSO and signIn.ssoFallback localization keys and the ssoFallback card action element id.

Patch Changes

@clerk/astro@4.1.2

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/backend@3.17.3

@clerk/backend@3.17.3

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0

@clerk/chrome-extension@3.1.83

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/clerk-js@6.32.0
    • @clerk/shared@4.32.0
    • @clerk/ui@1.33.0
    • @clerk/react@6.15.3

@clerk/electron@0.0.43

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/clerk-js@6.32.0
    • @clerk/shared@4.32.0
    • @clerk/react@6.15.3

@clerk/expo@4.6.7

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/clerk-js@6.32.0
    • @clerk/shared@4.32.0
    • @clerk/react@6.15.3

@clerk/expo-passkeys@2.0.19

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0

@clerk/express@2.1.68

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/backend@3.17.3

@clerk/fastify@3.1.78

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/backend@3.17.3

@clerk/hono@0.1.78

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/backend@3.17.3

@clerk/nextjs@7.9.3

Patch Changes

  • Add a note to the ClerkProvider, clerkMiddleware() and auth() doc comments explaining that npx clerk@latest init can provision temporary development keys without a Clerk account. Update the README prerequisites and installation section to say the same, replacing the statement that an existing Clerk application and account are required. (#9665) by @shane-kercheval

  • Updated dependencies [39782e3]:

    • @clerk/shared@4.32.0
    • @clerk/react@6.15.3
    • @clerk/backend@3.17.3

@clerk/nuxt@3.1.2

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/backend@3.17.3
    • @clerk/vue@2.5.2

@clerk/react@6.15.3

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0

@clerk/react-router@3.6.23

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/react@6.15.3
    • @clerk/backend@3.17.3

@clerk/tanstack-react-start@1.5.14

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/react@6.15.3
    • @clerk/backend@3.17.3

@clerk/testing@2.2.35

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0
    • @clerk/backend@3.17.3

@clerk/vue@2.5.2

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0

@clerk/headless@0.0.33

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0

@clerk/msw@0.0.69

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/shared@4.32.0

@clerk/swingset@0.0.46

Patch Changes

  • Updated dependencies [39782e3]:
    • @clerk/ui@1.33.0
    • @clerk/headless@0.0.33

@vercel

vercel Bot commented Sep 10, 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 11, 2026 1:34am UTC
swingset Ready Ready Preview Sep 11, 2026 1:34am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Sep 10, 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: ab59f4a5-f66d-4bb3-9826-1977859a5a8c

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 10, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

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

@clerk/electron-passkeys

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

@clerk/eslint-plugin

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

@clerk/expo

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

@clerk/expo-google-signin

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 463f540

@github-actions

github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

API Changes Report

Generated by Break Check on 2026-09-11T01:34:57.110Z

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 463f540.

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.

1 participant