ci(repo): Version packages - #9306
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-google-signin
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Contributor
API Changes Report
Summary
No API Changes DetectedAll packages have stable APIs with no detected changes. Report generated by Break Check Last ran on |
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
July 31, 2026 16:25
510e48e to
96fe42d
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
July 31, 2026 16:43
96fe42d to
1794700
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
July 31, 2026 17:19
1794700 to
35ddef3
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
July 31, 2026 19:02
35ddef3 to
22acb4b
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
July 31, 2026 20:18
22acb4b to
92d65ec
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 17:08
2f2e1f0 to
54d1eb6
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 17:36
54d1eb6 to
68eea6c
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 18:43
68eea6c to
e099c4e
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
August 4, 2026 07:01
e099c4e to
efdb432
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
August 4, 2026 13:18
efdb432 to
44034b0
Compare
clerk-cookie
force-pushed
the
changeset-release/main
branch
from
August 4, 2026 16:24
44034b0 to
792abc3
Compare
thiskevinwang
approved these changes
Aug 4, 2026
dstaley
approved these changes
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.26.0
Minor Changes
Support sign-in-or-sign-up combined flow with Clerk component (#7928) by @dmoerner
when strict enumeration protection is enabled.
On development instances,
<SignIn>now logs a warning when the sign-in-or-up flow is rendered on aninstance that has both password and strict enumeration protection enabled. In that configuration
visitors without an account are routed to the password screen and cannot complete a sign-up, so the
warning names both settings and how to resolve them.
Patch Changes
Recover from partitioned-cookie startup races by removing stale non-partitioned cookies when partitioned cookies become available. (#9286) by @thiskevinwang
Complete the Safari ITP cookie refresh when
setActive({ redirectUrl })navigates. (#9308) by @dmoernerSafari's ITP caps the client cookie at 7 days when it is re-issued from a fetch, so
setActive()routes its redirect through/v1/client/touchto restore the full lifetime. That navigation was immediately followed by a second one to the undecorated redirect URL, which superseded it and aborted the touch request before it completed, leaving the cookie capped.This applies to flows that pass
redirectUrlwithout anavigatecallback — email link sign-in, the password reset success screen, the OAuth popup flow, and directsetActive({ session, redirectUrl })calls — in apps where Clerk performs a full page navigation rather than handing off to a router. Users still landed on the correct page, so the only symptom was Safari sessions ending after 7 days and returning devices being challenged as if they were new.Updated dependencies [
5c81479]:@clerk/localizations@4.14.0
Minor Changes
Support sign-in-or-sign-up combined flow with Clerk component (#7928) by @dmoerner
when strict enumeration protection is enabled.
On development instances,
<SignIn>now logs a warning when the sign-in-or-up flow is rendered on aninstance that has both password and strict enumeration protection enabled. In that configuration
visitors without an account are routed to the password screen and cannot complete a sign-up, so the
warning names both settings and how to resolve them.
Patch Changes
5c81479]:@clerk/shared@4.26.0
Minor Changes
Support sign-in-or-sign-up combined flow with Clerk component (#7928) by @dmoerner
when strict enumeration protection is enabled.
On development instances,
<SignIn>now logs a warning when the sign-in-or-up flow is rendered on aninstance that has both password and strict enumeration protection enabled. In that configuration
visitors without an account are routed to the password screen and cannot complete a sign-up, so the
warning names both settings and how to resolve them.
@clerk/ui@1.28.0
Minor Changes
Support sign-in-or-sign-up combined flow with Clerk component (#7928) by @dmoerner
when strict enumeration protection is enabled.
On development instances,
<SignIn>now logs a warning when the sign-in-or-up flow is rendered on aninstance that has both password and strict enumeration protection enabled. In that configuration
visitors without an account are routed to the password screen and cannot complete a sign-up, so the
warning names both settings and how to resolve them.
Patch Changes
fix(ui): Avoid races between email link tabs when using sign up if missing (#9328) by @dmoerner
Updated dependencies [
5c81479]:@clerk/astro@4.0.6
Patch Changes
a601cd7,5c81479]:@clerk/backend@3.15.1
Patch Changes
Add the optional
emailAddressIdentificationStatusandphoneNumberIdentificationStatusparameters toCreateUserParams. The Backend API has supported these arrays onPOST /v1/userssince they shipped, butcreateUser()had no way to pass them, so every email address and phone number was necessarily created verified. Each array runs parallel toemailAddress/phoneNumber— one item per identifier, applied by position — and an item set to'reserved'creates that identifier unverified but still usable for sign-in and locked so no other user can claim it. (#9305) by @dmoernerThe
createUser()documentation is corrected accordingly: it stated unconditionally that created email addresses and phone numbers are automatically verified, which is only the default.Updated dependencies [
5c81479]:@clerk/chrome-extension@3.1.65
Patch Changes
bbe51ff,bf1b62a,5c81479,83a8fc5,7f0cac8]:@clerk/electron@0.0.26
Patch Changes
bbe51ff,bf1b62a,5c81479,7f0cac8]:@clerk/expo@4.2.1
Patch Changes
bbe51ff,bf1b62a,5c81479,7f0cac8]:@clerk/expo-passkeys@2.0.5
Patch Changes
5c81479]:@clerk/express@2.1.50
Patch Changes
Respond with 400 Bad Request instead of surfacing a 500 when an incoming request cannot be represented as a fetch
Request. Vulnerability-scanner probes such as hostless//request targets, targets that parse as credentialed URLs, and forbidden methods like TRACE previously threw inside the middleware and polluted error logs. (#9290) by @wobsorianoUpdated dependencies [
a601cd7,5c81479]:@clerk/fastify@3.1.60
Patch Changes
Respond with 400 Bad Request instead of surfacing a 500 when an incoming request cannot be represented as a fetch
Request. Vulnerability-scanner probes such as hostless//request targets, targets that parse as credentialed URLs, and forbidden methods like TRACE previously threw inside the middleware and polluted error logs. (#9290) by @wobsorianoUpdated dependencies [
a601cd7,5c81479]:@clerk/hono@0.1.60
Patch Changes
a601cd7,5c81479]:@clerk/nextjs@7.6.5
Patch Changes
a601cd7,bbe51ff,5c81479]:@clerk/nuxt@3.0.2
Patch Changes
a601cd7,5c81479]:@clerk/react@6.12.11
Patch Changes
Allow
ClerkProviderto omitpublishableKeywhen it is supplied throughVITE_CLERK_PUBLISHABLE_KEYorCLERK_PUBLISHABLE_KEY. (#9314) by @SarahSoutoulUpdated dependencies [
5c81479]:@clerk/react-router@3.6.4
Patch Changes
a601cd7,bbe51ff,5c81479]:@clerk/tanstack-react-start@1.4.27
Patch Changes
a601cd7,bbe51ff,5c81479]:@clerk/testing@2.2.17
Patch Changes
a601cd7,5c81479]:@clerk/vue@2.4.23
Patch Changes
5c81479]:@clerk/headless@0.0.19
Patch Changes
5c81479]:@clerk/msw@0.0.55
Patch Changes
5c81479]:@clerk/swingset@0.0.29
Patch Changes
5c81479,83a8fc5]: