Skip to content

ci(repo): Version packages#8438

Merged
jacekradko merged 1 commit intomainfrom
changeset-release/main
May 1, 2026
Merged

ci(repo): Version packages#8438
jacekradko merged 1 commit intomainfrom
changeset-release/main

Conversation

@clerk-cookie
Copy link
Copy Markdown
Collaborator

@clerk-cookie clerk-cookie commented May 1, 2026

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/astro@3.1.0

Minor Changes

  • Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

    • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
    • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

    The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

  • Expose OAuthConsent as a public component export for Astro. (#8381) by @wobsoriano

    Example:

    ---
    import { OAuthConsent } from '@clerk/astro/components';
    ---
    
    <OAuthConsent />

Patch Changes

@clerk/clerk-js@6.8.0

Minor Changes

  • Add internal API methods to manage enterprise connections (#8421) by @LauraBeatris

  • Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

    Example:

    import { OAuthConsent } from '@clerk/react';
    
    export default function Page() {
      return <OAuthConsent />;
    }

Patch Changes

@clerk/nextjs@7.3.0

Minor Changes

  • Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

    Example:

    import { OAuthConsent } from '@clerk/react';
    
    export default function Page() {
      return <OAuthConsent />;
    }

Patch Changes

  • Updated dependencies [785f057, 90beaeb, 244920d]:
    • @clerk/shared@4.9.0
    • @clerk/react@6.5.0
    • @clerk/backend@3.4.4

@clerk/nuxt@2.3.0

Minor Changes

  • Expose OAuthConsent as a public component export for Vue and Nuxt. (#8381) by @wobsoriano

    Example:

    <script setup lang="ts">
    import { OAuthConsent } from '@clerk/vue';
    </script>
    
    <template>
      <OAuthConsent />
    </template>
  • Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

    • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
    • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

    The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

Patch Changes

@clerk/react@6.5.0

Minor Changes

  • Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

    Example:

    import { OAuthConsent } from '@clerk/react';
    
    export default function Page() {
      return <OAuthConsent />;
    }

Patch Changes

@clerk/react-router@3.2.0

Minor Changes

  • Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

    • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
    • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

    The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

  • Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

    Example:

    import { OAuthConsent } from '@clerk/react';
    
    export default function Page() {
      return <OAuthConsent />;
    }

Patch Changes

  • Updated dependencies [785f057, 90beaeb, 244920d]:
    • @clerk/shared@4.9.0
    • @clerk/react@6.5.0
    • @clerk/backend@3.4.4

@clerk/shared@4.9.0

Minor Changes

  • Add internal API methods to manage enterprise connections (#8421) by @LauraBeatris

  • Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

    Example:

    import { OAuthConsent } from '@clerk/react';
    
    export default function Page() {
      return <OAuthConsent />;
    }

Patch Changes

  • Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

    • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
    • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

    The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

@clerk/tanstack-react-start@1.2.0

Minor Changes

  • Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

    • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
    • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
    • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

    The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

  • Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

    Example:

    import { OAuthConsent } from '@clerk/react';
    
    export default function Page() {
      return <OAuthConsent />;
    }

Patch Changes

  • Updated dependencies [785f057, 90beaeb, 244920d]:
    • @clerk/shared@4.9.0
    • @clerk/react@6.5.0
    • @clerk/backend@3.4.4

@clerk/ui@1.7.0

Minor Changes

  • Render OAuthConsent organization selector from user:org:read scope. (#8415) by @wobsoriano

  • Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

    Example:

    import { OAuthConsent } from '@clerk/react';
    
    export default function Page() {
      return <OAuthConsent />;
    }

Patch Changes

@clerk/vue@2.1.0

Minor Changes

  • Expose OAuthConsent as a public component export for Vue and Nuxt. (#8381) by @wobsoriano

    Example:

    <script setup lang="ts">
    import { OAuthConsent } from '@clerk/vue';
    </script>
    
    <template>
      <OAuthConsent />
    </template>

Patch Changes

@clerk/backend@3.4.4

Patch Changes

@clerk/chrome-extension@3.1.21

Patch Changes

@clerk/expo@3.2.7

Patch Changes

  • Updated dependencies [785f057, 90beaeb, 244920d]:
    • @clerk/clerk-js@6.8.0
    • @clerk/shared@4.9.0
    • @clerk/react@6.5.0

@clerk/expo-passkeys@1.0.20

Patch Changes

@clerk/express@2.1.12

Patch Changes

@clerk/fastify@3.1.22

Patch Changes

@clerk/hono@0.1.22

Patch Changes

@clerk/localizations@4.5.8

Patch Changes

@clerk/testing@2.0.24

Patch Changes

@clerk/msw@0.0.20

Patch Changes

@vercel
Copy link
Copy Markdown

vercel Bot commented May 1, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clerk-js-sandbox Ready Ready Preview, Comment May 1, 2026 6:25am

Request Review

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 1, 2026

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8438

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 1a6484d

@jacekradko jacekradko merged commit b2e702e into main May 1, 2026
9 checks passed
@jacekradko jacekradko deleted the changeset-release/main branch May 1, 2026 15:32
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.

2 participants