This release introduces support for Clerk Protect mid-flow SDK challenges during sign-up and sign-in flows, adding a new status value and corresponding fields to handle iterative challenges.

@clerk/nextjs@7.5.14

Jul 7, 2026

This patch deprecates `createRouteMatcher()` in favor of more robust resource-based authentication checks within individual components or routes. Dependencies for shared, react, and backend packages have also been updated.

@clerk/expo-passkeys@1.2.1

Jul 7, 2026

This patch release primarily focuses on updating internal dependencies, specifically bumping @clerk/shared to version 4.25.0.

@clerk/express@2.1.37

Jul 7, 2026

This patch release primarily involves updating internal dependencies, specifically @clerk/shared to v4.25.0 and @clerk/backend to v3.11.1.

@clerk/hono@0.1.47

Jul 7, 2026

This patch release primarily focuses on updating internal dependencies, specifically @clerk/shared and @clerk/backend, to newer versions.

@clerk/ui@1.25.06 fixes2 features

Jul 7, 2026

This release introduces support for Clerk Protect mid-flow challenges during sign-up and sign-in, enhancing fraud prevention capabilities. Numerous UI and state management bugs related to payment forms, modals, tooltips, and the new Protect flow have also been resolved.

@clerk/electron@0.0.10

Jul 7, 2026

This patch release focuses on updating internal dependencies across several Clerk packages, including @clerk/shared, @clerk/clerk-js, and @clerk/react.

@clerk/fastify@3.1.47

Jul 7, 2026

This patch release primarily focuses on updating internal dependencies, specifically @clerk/shared and @clerk/backend, to newer versions.

@clerk/expo@3.7.1

Jul 7, 2026

This patch release primarily consists of dependency updates across several Clerk packages, including @clerk/shared, @clerk/clerk-js, and @clerk/react.

@clerk/chrome-extension@3.1.49

Jul 7, 2026

This patch release primarily consists of dependency updates across several Clerk packages, including @clerk/ui, @clerk/shared, @clerk/clerk-js, and @clerk/react.

@clerk/react-router@3.5.6

Jul 7, 2026

This patch release focuses on updating internal dependencies across several Clerk packages, including shared, react, and backend.

@clerk/shared@4.25.01 fix3 features

Jul 7, 2026

This release introduces support for Clerk Protect mid-flow SDK challenges during sign-up and sign-in flows, enhancing antifraud capabilities. It also includes minor polish fixes for the Protect check UI.

@clerk/localizations@4.13.03 features

Jul 7, 2026

This release introduces support for Clerk Protect mid-flow SDK challenges during sign-up and sign-in flows, adding new status indicators and submission methods for handling antifraud challenges.

@clerk/testing@2.2.4

Jul 7, 2026

This patch release primarily focuses on updating internal dependencies, specifically @clerk/shared and @clerk/backend, to newer versions.

@clerk/tanstack-react-start@1.4.14

Jul 7, 2026

This patch release focuses on updating internal dependencies across several Clerk packages, including shared, react, and backend.

@clerk/nuxt@2.6.13

Jul 7, 2026

This patch deprecates `createRouteMatcher()` encouraging users to adopt Nuxt's native route matching for better integration. Dependencies including @clerk/shared, @clerk/backend, and @clerk/vue have also been updated.

@clerk/vue@2.4.12

Jul 7, 2026

This patch release primarily involves updating internal dependencies, specifically releasing @clerk/shared to version 4.25.0.

@clerk/react@6.12.03 features

Jul 7, 2026

This release introduces support for Clerk Protect mid-flow SDK challenges during sign-up and sign-in flows, enhancing antifraud capabilities. The update includes type-only changes for sign-in status handling.

@clerk/astro@3.4.13

Jul 7, 2026

This patch release primarily consists of dependency updates for @clerk/shared and @clerk/backend.

@clerk/clerk-js@6.24.01 fix1 feature

Jul 6, 2026

This release introduces new fields for SAML enterprise connections regarding IdP certificate validity and fixes a bug related to session token freshness comparison.

@clerk/chrome-extension@3.1.48

Jul 6, 2026

This patch release primarily consists of dependency updates across several Clerk packages, including @clerk/ui, @clerk/clerk-js, @clerk/shared, and @clerk/react.

Common Errors

SerovalDeserializationError1 report

SerovalDeserializationError in Clerk often arises from trying to serialize complex data structures like dates or functions stored in user metadata. To fix this, either serialize these values into simpler formats such as ISO strings or primitive data types before storing them in Clerk, or exclude them entirely from the metadata. Ensure the data passed can be handled by the serialization/deserialization process.

SerovalMissingInstanceError1 report

The "SerovalMissingInstanceError" in Clerk often arises when your metadata (public or private) contains complex data structures like Promises, Dates, or custom class instances that Seroval (Clerk's serialization library) can't natively serialize. To fix this, either convert these complex data types into simple serializable formats like strings or numbers *before* storing them in metadata, or implement a custom serializer/deserializer for those types within your Clerk app, as outlined in Clerk's documentation.

SerovalMissingPluginError1 report

The "SerovalMissingPluginError" in Clerk typically arises when the serialization library (Seroval) used by Clerk lacks a plugin to handle specific data types present in your application's Clerk data, such as custom objects in public or private metadata. To fix this, identify the problematic data type and install the corresponding Seroval plugin, for example, use `npm install seroval-plugins-arraybuffer` if encountering ArrayBuffer errors and register it with `registerSerovalPlugins([ArrayBufferPlugin])` during your application's initialization. Ensure the plugins are installed on both server and client if server-side rendering is involved.

SerovalMissingReferenceError1 report

The "SerovalMissingReferenceError" in Clerk often arises when serializing complex objects, particularly user metadata, that contain circular references or unserializable data types like functions or symbols. To fix this, ensure your public and private metadata only contain primitive data types (strings, numbers, booleans) or serializable objects. Consider using a custom serialization function (like `JSON.stringify` with a replacer) to prune or transform the metadata before passing it to Clerk functions like `getAuth` or user update methods.

SerovalMissingReferenceForIdError1 report

The "SerovalMissingReferenceForIdError" in Clerk often arises when the server attempts to serialize user metadata containing circular references or complex data structures that Seroval (Clerk's serialization library) cannot handle by default. To resolve this, either simplify the problematic metadata fields (e.g., flatten nested objects, remove circular references) or configure Clerk's `serialize` option to use a more robust serialization method like `JSON.stringify` for user metadata. Verify that custom afterAuth/beforeAuth functions are not modifying the clerk object improperly which is creating the error.

SerovalParserError1 report

SerovalParserError in Clerk often arises when private metadata contains unserializable data structures like functions or circular references. To fix this, either remove unserializable data from your private metadata or use a serialization library such as `superjson` to transform the data into a serializable format before saving it to Clerk, and deserialize it upon retrieval. Also ensure your `clerk.config.ts` or equivalent is correctly configured to handle custom serialization if needed.