Clerk Changelog

Fastify, the fast and low overhead web framework for Node.js, has recently shipped Fastify v5. In order to support Fastify v5 a new major version of @clerk/fastify had to be released. With Clerk's Fastify SDK 2.0 comes full support for Fastify v5 and no breaking changes for the Clerk SDK itself.

If you're using Fastify and @clerk/fastify, you can update like so:

1. Follow the official Fastify v5 migration guide⁠
2. Install the latest version of @clerk/fastify

   npm install @clerk/fastify@latest

3. You're done! No further changes needed

@clerk/fastify@^2.0.0 only supports Fastify v5 or later, if you want/need to continue using Fastify v4, please stick with @clerk/fastify@^1.0.0.

We're excited to announce the release of @clerk/express, our latest SDK designed specifically for Express applications⁠.

The SDK comes fully equipped with server utilities and low level utilities for any of your custom flows.

Here's an example on how simple it is to protect a route with our Express SDK:

import express from 'express'
import { requireAuth } from '@clerk/express'

const app = express()

// if the user is not signed in, they will be redirected to /sign-in automatically
app.get('/protected', requireAuth({ signInUrl: '/sign-in' }), (req, res) => {
  return res.json({ userId: req.auth.userId })
})

Deprecating @clerk/clerk-sdk-node

With this release, we are initiating the process to deprecate @clerk/clerk-sdk-node.

During this transition period, we intend to:

• Continue to provide critical patches and bug fixes for @clerk/clerk-sdk-node
• Pause adding new features to @clerk/clerk-sdk-node
• Focus our development efforts on @clerk/express

The transition to end @clerk/clerk-sdk-node support ends on January 8, 2025. To ensure a smooth transition, we've prepared a comprehensive Migration Guide with step-by-step instructions.

Upgrade today and experience enhanced authentication and user management in your Express projects with Clerk!

We're pleased to announce the release of our server-side Python SDK⁠!

With this launch, Python developers can more easily interface with the Clerk Backend API to manage users, organizations, and sessions.

import asyncio
from clerk_backend_api import Clerk

async def main():
    sdk = Clerk(
        bearer_auth="<YOUR_BEARER_TOKEN_HERE>",
    )
    res = await sdk.email_addresses.get_async(
        email_address_id="email_address_id_example"
    )
    if res is not None:
        # handle response
        pass

asyncio.run(main())

This release also makes it straightforward to authenticate backend requests in Django, Flask, and other Python web frameworks:

import os
import httpx
from clerk_backend_api import Clerk
from clerk_backend_api.jwks_helpers import AuthenticateRequestOptions

def is_signed_in(request: httpx.Request):
    sdk = Clerk(bearer_auth=os.getenv('CLERK_SECRET_KEY'))
    request_state = sdk.authenticate_request(
        request,
        AuthenticateRequestOptions(
            authorized_parties=['https://example.com']
        )
    )
    return request_state.is_signed_in

You can pip install the new clerk-backend-api⁠ module in any Python 3.8+ application to get started. To help you from there, we've prepared detailed reference documentation⁠ in the SDK GitHub repository.

Special thanks to Speakeasy⁠ for partnering with us on this SDK release 🎉!

We've made an update to the Clerk Dashboard⁠ that consolidates "Social Connections" and "Enterprise Connections" into one unified view.

We found through working with our customer's that this distinction was unclear and having to manage these in different places felt unintuitive. Going forward you can simply select the Add connection and choose whether you're attempting to set up a connection for all of your users, or only for users of a specific domain.

We're excited to announce that Clerk has teamed up with Coinbase to make building Web3 applications easier. As a first step, Clerk released a new API today that allows developers to quickly integrate a customer's Coinbase Wallet⁠ with their Clerk user account. In addition, Clerk's embeddable <SignUp/> and <SignIn/> components now support authentication with Coinbase Wallet. Read our documentation to get started.

<SignIn/> with Coinbase Wallet and <UserProfile/> with Coinbase connection:

Coinbase Wallet is a user-friendly, self-custodial solution that simplifies onchain transactions. Secured by Passkeys, it allows applications to cover gas fees, enabling users to pay with their Coinbase balance. This streamlined approach makes blockchain interactions more accessible, eliminating complex setups and lowering entry barriers to use products onchain.

Developers building with Clerk can now seamlessly connect user management with Coinbase Wallet functionality. This offers a path to building Web3 applications that prioritize speed of development, security, and ease of use.

We envision a future where identity-based enablement allows for more autonomous, efficient, and secure payment systems. By leveraging Clerk's user management capabilities, developers building on Coinbase Developer Platform are provided with a powerful suite of tools that goes beyond wallet integration – including robust session management, authorization controls, and tools for better customer engagement and retention.

We're eager to see how developers use these tools to more easily create new possibilities in Web3, and we're thrilled to deepen our collaboration with Coinbase Developer Platform to simplify onchain application development.

Administrators now have more control over the behavior of <UserProfile /> when their users authenticate via an Enterprise Connection. This is particularly useful when a B2B customer has strict policies regarding the management of user account information through their IdP (Identity Provider).

Moving forward, additional identifiers will no longer be allowed by default. For existing connections, you are able to adjust this setting in the Advanced tab⁠ of each Enterprise Connection in the dashboard.