Clerk Changelog

We've added a new Payments tab to both user and organization detail pages in the Dashboard. This feature gives you complete visibility into all subscription payment attempts, making it easier to track billing activity and troubleshoot payment issues.

For all you up-and-to-the-right folks, you can now view the total number of users who have ever signed up for your application directly from the dashboard, in this new handy chart. This new chart makes it easy to track your all time user growth at a glance and bask in that sweet-sweet hockey stick inflection.

We've completely redesigned the Clerk Dashboard's overview page to focus on User Growth. Previously, we only tracked basic data points, but now we provide comprehensive retention and churn metrics that give you deeper insights into your user base.

In the new charts we now show detailed insights like...

• New Users - New Users
• Reactivated Users - Inactive users who became active again
• Retained Users - Existing users who remained active this period
• Retained churned - Retained users who became inactive this period
• Reactivated churned - Reactivated users that churned this period
• New users churned - New users who churned this period

Beyond the enhanced growth charts, we've introduced flexible time-based filtering options. You can now analyze your data across different time periods (Daily, Weekly, Monthly) and customize date ranges to gain deeper insights into your application's performance and user behavior patterns.

Stay tuned for more planned improvements.

When we launched Billing, the Connect to Stripe flow was locked to US-only businesses. Today, we've removed that constraint and Billing is now available in any country that's supported by Stripe (see global availability⁠).

Select your Business Location in the Connect to Stripe flow. If you find that the Business Location drop-down is still locked, you may need to disconnect the associated Stripe account and set up a fresh connection.

Start building your global business with Clerk Billing today.

Key changes in v2 include a revamped structure for organization-related claims, now nested under the o claim for improved clarity and reduced token size. Additionally, a new v claim explicitly identifies the token version.

As of today, April 14, 2025, version 1 of the session token format is deprecated. You can update to version 2 via the Updates page⁠ in your Clerk Dashboard.

For a detailed breakdown of all claims available in v2 and how they differ from v1, please refer to our Session Tokens documentation.

We strongly recommend using one of our SDKs that support API version 2025-04-10 to handle decoding reliably.

Clerk is now supported as a Supabase third-party authentication provider⁠. This first-class integration allows Supabase to accept Clerk-signed session tokens, removing the need to create a custom JWT template and generate a specific token when interacting with Supabase's APIs.

Now, all you need to do is pass Clerk's session token to Supabase's client:

import { createClient } from '@supabase/supabase-js'
import { auth } from '@clerk/nextjs/server'

const supabase = createClient(
  process.env.NEXT_PUBLIC_SUPABASE_URL!,
  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
  {
    async accessToken() {
      return (await auth()).getToken()
    },
  },
)

Enable the integration

To get started with Clerk and Supabase:

1. Visit the Clerk dashboard⁠ and go through the setup flow
2. Copy your Clerk instance domain into Supabase's Third-party auth settings⁠

For more information, visit the Supabase Integration documentation page. We can't wait to see what you build with Clerk and Supabase!