Skip to content

ci(repo): Version packages #6541

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 14, 2025
Merged

ci(repo): Version packages #6541

merged 1 commit into from
Aug 14, 2025

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented Aug 13, 2025

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/[email protected]

Minor Changes

  • Remove secret in favor of token in m2m response. (#6542) by @wobsoriano

    Before:

    const result = await clerkClient.m2mTokens.create();
    
    console.log(result.secret);

    After:

    const result = await clerkClient.m2mTokens.create();
    
    console.log(result.token);
  • Rename M2M namespace from m2mTokens to m2m in Backend API client (#6544) by @wobsoriano

    Before:

    clerkClient.m2mTokens.create();
    
    clerkClient.m2mTokens.revoke();
    
    clerkClient.m2mTokens.verifySecret({ secret: 'ak_xxx' });

    After:

    clerkClient.m2m.createToken();
    
    clerkClient.m2m.revokeToken();
    
    clerkClient.m2m.verifyToken({ token: 'ak_xxx' });

    The verifySecret() method is removed. Please use .verifyToken() instead.

  • Deprecates clerkClient.m2mTokens.verifySecret({ secret: 'mt_xxx' }) in favor or clerkClient.m2mTokens.verifyToken({ token: 'mt_xxx' }) (#6536) by @wobsoriano

Patch Changes

@clerk/[email protected]

Minor Changes

  • Add navigate parameter to clerk.setActive() for custom navigation before the session and/or organization is set. (#6486) by @LauraBeatris

    It's useful for handling pending session tasks for after-auth flows:

    await clerk.setActive({
      session,
      navigate: async ({ session }) => {
        const currentTask = session.currentTask;
        if (currentTask) {
          await router.push(`/onboarding/${currentTask.key}`);
          return;
        }
    
        await router.push('/dashboard');
      },
    });

Patch Changes

@clerk/[email protected]

Minor Changes

Patch Changes

@clerk/[email protected]

Minor Changes

Patch Changes

@clerk/[email protected]

Minor Changes

Patch Changes

@clerk/[email protected]

Minor Changes

Patch Changes

@clerk/[email protected]

Minor Changes

Patch Changes

@clerk/[email protected]

Minor Changes

  • Add navigate parameter to clerk.setActive() for custom navigation before the session and/or organization is set. (#6486) by @LauraBeatris

    It's useful for handling pending session tasks for after-auth flows:

    await clerk.setActive({
      session,
      navigate: async ({ session }) => {
        const currentTask = session.currentTask;
        if (currentTask) {
          await router.push(`/onboarding/${currentTask.key}`);
          return;
        }
    
        await router.push('/dashboard');
      },
    });

Patch Changes

@clerk/[email protected]

Minor Changes

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

Summary by CodeRabbit

  • New Features

    • Added optional navigate callback to setActive for custom pre-activation routing.
  • Refactor

    • Renamed UI component RedirectToTask to RedirectToTasks across React, Next.js, Remix, React Router, Vue, and TanStack integrations.
    • Updated M2M backend API: m2mTokens namespace renamed to m2m; create/revoke methods renamed; verifySecret replaced by verifyToken; responses now return token instead of secret.
  • Chores

    • Version bumps and dependency updates across multiple SDKs and integrations; no functional changes beyond those noted above.

Copy link

vercel bot commented Aug 13, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project Deployment Preview Comments Updated (UTC)
clerk-js-sandbox Ready Preview Comment Aug 14, 2025 0:50am

Copy link

pkg-pr-new bot commented Aug 13, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6541

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6541

@clerk/clerk-expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/clerk-react

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

@clerk/react-router

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

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6541

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6541

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6541

@clerk/upgrade

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

@clerk/vue

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

commit: e6b4292

Copy link
Contributor

coderabbitai bot commented Aug 13, 2025

📝 Walkthrough

Walkthrough

Multiple .changeset files were removed and many package CHANGELOG.md and package.json version fields were updated across the monorepo. Public API changes documented in changelogs include: backend M2M surface renames (m2mTokens → m2m; create response secret → token; verifySecret → verifyToken), addition of an optional navigate parameter to Clerk.setActive, renaming RedirectToTask → RedirectToTasks in several UI packages, and a Next.js telemetry event KEYLESS_ENV_DRIFT_DETECTED. Several packages list dependency updates to @clerk/* packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

  • wobsoriano
  • panteliselef

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled
  • Linear integration is disabled by default for public repositories

You can enable these settings in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 0357f13 and e6b4292.

📒 Files selected for processing (50)
  • .changeset/chatty-kings-raise.md (0 hunks)
  • .changeset/rich-donuts-agree.md (0 hunks)
  • .changeset/serious-chicken-report.md (0 hunks)
  • .changeset/small-adults-crash.md (0 hunks)
  • .changeset/upset-sides-kneel.md (0 hunks)
  • .changeset/warm-rocks-flow.md (0 hunks)
  • packages/agent-toolkit/CHANGELOG.md (1 hunks)
  • packages/agent-toolkit/package.json (1 hunks)
  • packages/astro/CHANGELOG.md (1 hunks)
  • packages/astro/package.json (1 hunks)
  • packages/backend/CHANGELOG.md (1 hunks)
  • packages/backend/package.json (1 hunks)
  • packages/chrome-extension/CHANGELOG.md (1 hunks)
  • packages/chrome-extension/package.json (1 hunks)
  • packages/clerk-js/CHANGELOG.md (1 hunks)
  • packages/clerk-js/package.json (1 hunks)
  • packages/elements/CHANGELOG.md (1 hunks)
  • packages/elements/package.json (1 hunks)
  • packages/expo-passkeys/CHANGELOG.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
  • packages/expo/CHANGELOG.md (1 hunks)
  • packages/expo/package.json (1 hunks)
  • packages/express/CHANGELOG.md (1 hunks)
  • packages/express/package.json (1 hunks)
  • packages/fastify/CHANGELOG.md (1 hunks)
  • packages/fastify/package.json (1 hunks)
  • packages/localizations/CHANGELOG.md (1 hunks)
  • packages/localizations/package.json (1 hunks)
  • packages/nextjs/CHANGELOG.md (1 hunks)
  • packages/nextjs/package.json (1 hunks)
  • packages/nuxt/CHANGELOG.md (1 hunks)
  • packages/nuxt/package.json (1 hunks)
  • packages/react-router/CHANGELOG.md (1 hunks)
  • packages/react-router/package.json (1 hunks)
  • packages/react/CHANGELOG.md (1 hunks)
  • packages/react/package.json (1 hunks)
  • packages/remix/CHANGELOG.md (1 hunks)
  • packages/remix/package.json (1 hunks)
  • packages/shared/CHANGELOG.md (1 hunks)
  • packages/shared/package.json (1 hunks)
  • packages/tanstack-react-start/CHANGELOG.md (1 hunks)
  • packages/tanstack-react-start/package.json (1 hunks)
  • packages/testing/CHANGELOG.md (1 hunks)
  • packages/testing/package.json (1 hunks)
  • packages/themes/CHANGELOG.md (1 hunks)
  • packages/themes/package.json (1 hunks)
  • packages/types/CHANGELOG.md (1 hunks)
  • packages/types/package.json (1 hunks)
  • packages/vue/CHANGELOG.md (1 hunks)
  • packages/vue/package.json (1 hunks)
💤 Files with no reviewable changes (6)
  • .changeset/warm-rocks-flow.md
  • .changeset/rich-donuts-agree.md
  • .changeset/small-adults-crash.md
  • .changeset/upset-sides-kneel.md
  • .changeset/serious-chicken-report.md
  • .changeset/chatty-kings-raise.md
✅ Files skipped from review due to trivial changes (8)
  • packages/react/package.json
  • packages/clerk-js/package.json
  • packages/chrome-extension/CHANGELOG.md
  • packages/chrome-extension/package.json
  • packages/express/CHANGELOG.md
  • packages/elements/package.json
  • packages/backend/package.json
  • packages/react-router/CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (36)
  • packages/astro/package.json
  • packages/nuxt/package.json
  • packages/expo/package.json
  • packages/react-router/package.json
  • packages/localizations/package.json
  • packages/express/package.json
  • packages/tanstack-react-start/package.json
  • packages/themes/package.json
  • packages/agent-toolkit/package.json
  • packages/vue/package.json
  • packages/shared/package.json
  • packages/remix/package.json
  • packages/types/package.json
  • packages/elements/CHANGELOG.md
  • packages/expo-passkeys/package.json
  • packages/localizations/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/testing/package.json
  • packages/themes/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/nextjs/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/fastify/package.json
  • packages/shared/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep-cloud-platform/scan

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot force-pushed the changeset-release/main branch from 536126e to 400317a Compare August 13, 2025 20:46
Copy link
Contributor

coderabbitai bot commented Aug 13, 2025

Caution

Review failed

Failed to post review comments.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69498df and 536126e.

📒 Files selected for processing (47)
  • .changeset/rich-donuts-agree.md (0 hunks)
  • .changeset/upset-sides-kneel.md (0 hunks)
  • .changeset/warm-rocks-flow.md (0 hunks)
  • packages/agent-toolkit/CHANGELOG.md (1 hunks)
  • packages/agent-toolkit/package.json (1 hunks)
  • packages/astro/CHANGELOG.md (1 hunks)
  • packages/astro/package.json (1 hunks)
  • packages/backend/CHANGELOG.md (1 hunks)
  • packages/backend/package.json (1 hunks)
  • packages/chrome-extension/CHANGELOG.md (1 hunks)
  • packages/chrome-extension/package.json (1 hunks)
  • packages/clerk-js/CHANGELOG.md (1 hunks)
  • packages/clerk-js/package.json (1 hunks)
  • packages/elements/CHANGELOG.md (1 hunks)
  • packages/elements/package.json (1 hunks)
  • packages/expo-passkeys/CHANGELOG.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
  • packages/expo/CHANGELOG.md (1 hunks)
  • packages/expo/package.json (1 hunks)
  • packages/express/CHANGELOG.md (1 hunks)
  • packages/express/package.json (1 hunks)
  • packages/fastify/CHANGELOG.md (1 hunks)
  • packages/fastify/package.json (1 hunks)
  • packages/localizations/CHANGELOG.md (1 hunks)
  • packages/localizations/package.json (1 hunks)
  • packages/nextjs/CHANGELOG.md (1 hunks)
  • packages/nextjs/package.json (1 hunks)
  • packages/nuxt/CHANGELOG.md (1 hunks)
  • packages/nuxt/package.json (1 hunks)
  • packages/react-router/CHANGELOG.md (1 hunks)
  • packages/react-router/package.json (1 hunks)
  • packages/react/CHANGELOG.md (1 hunks)
  • packages/react/package.json (1 hunks)
  • packages/remix/CHANGELOG.md (1 hunks)
  • packages/remix/package.json (1 hunks)
  • packages/shared/CHANGELOG.md (1 hunks)
  • packages/shared/package.json (1 hunks)
  • packages/tanstack-react-start/CHANGELOG.md (1 hunks)
  • packages/tanstack-react-start/package.json (1 hunks)
  • packages/testing/CHANGELOG.md (1 hunks)
  • packages/testing/package.json (1 hunks)
  • packages/themes/CHANGELOG.md (1 hunks)
  • packages/themes/package.json (1 hunks)
  • packages/types/CHANGELOG.md (1 hunks)
  • packages/types/package.json (1 hunks)
  • packages/vue/CHANGELOG.md (1 hunks)
  • packages/vue/package.json (1 hunks)
💤 Files with no reviewable changes (3)
  • .changeset/warm-rocks-flow.md
  • .changeset/rich-donuts-agree.md
  • .changeset/upset-sides-kneel.md
🧰 Additional context used
📓 Path-based instructions (5)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/nuxt/package.json
  • packages/tanstack-react-start/package.json
  • packages/testing/package.json
  • packages/elements/package.json
  • packages/astro/package.json
  • packages/clerk-js/package.json
  • packages/express/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/agent-toolkit/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/localizations/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/expo-passkeys/package.json
  • packages/remix/package.json
  • packages/chrome-extension/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/shared/package.json
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/package.json
  • packages/expo/package.json
  • packages/nuxt/CHANGELOG.md
  • packages/react-router/package.json
  • packages/fastify/CHANGELOG.md
  • packages/themes/package.json
  • packages/react-router/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/nextjs/package.json
  • packages/nextjs/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/vue/package.json
  • packages/remix/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/express/CHANGELOG.md
packages/*/package.json

📄 CodeRabbit Inference Engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/nuxt/package.json
  • packages/tanstack-react-start/package.json
  • packages/testing/package.json
  • packages/elements/package.json
  • packages/astro/package.json
  • packages/clerk-js/package.json
  • packages/express/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/agent-toolkit/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/expo-passkeys/package.json
  • packages/remix/package.json
  • packages/chrome-extension/package.json
  • packages/shared/package.json
  • packages/fastify/package.json
  • packages/expo/package.json
  • packages/react-router/package.json
  • packages/themes/package.json
  • packages/nextjs/package.json
  • packages/vue/package.json
**/*

⚙️ CodeRabbit Configuration File

If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.

Files:

  • packages/nuxt/package.json
  • packages/tanstack-react-start/package.json
  • packages/testing/package.json
  • packages/elements/package.json
  • packages/astro/package.json
  • packages/clerk-js/package.json
  • packages/express/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/agent-toolkit/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/localizations/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/expo-passkeys/package.json
  • packages/remix/package.json
  • packages/chrome-extension/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/shared/package.json
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/package.json
  • packages/expo/package.json
  • packages/nuxt/CHANGELOG.md
  • packages/react-router/package.json
  • packages/fastify/CHANGELOG.md
  • packages/themes/package.json
  • packages/react-router/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/nextjs/package.json
  • packages/nextjs/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/vue/package.json
  • packages/remix/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/express/CHANGELOG.md
packages/localizations/**/*

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Localization files must be placed in 'packages/localizations/'.

Files:

  • packages/localizations/package.json
  • packages/localizations/CHANGELOG.md
packages/**/CHANGELOG.md

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Maintain detailed changelogs

Files:

  • packages/localizations/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/express/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: Build Packages
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep/ci
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (53)
packages/tanstack-react-start/package.json (2)

3-3: Semver bump looks correct for a public API rename

Minor bump to 0.22.0 aligns with RedirectToTask → RedirectToTasks rename noted in the changelog.


3-3: All code exports/usages migrated; CHANGELOG entry for 0.22.0 present

Short summary: ripgrep shows no remaining source/test usages of "RedirectToTask" — only historical mentions remain in several CHANGELOG.md files. packages/tanstack-react-start/CHANGELOG.md contains the "## 0.22.0" header.

Files containing "RedirectToTask" (historical changelog mentions):

  • packages/vue/CHANGELOG.md (lines with "Rename" and "Introduce")
  • packages/tanstack-react-start/CHANGELOG.md (rename entry)
  • packages/react/CHANGELOG.md (rename and introduce entries)
  • packages/nextjs/CHANGELOG.md (rename and introduce entries)

Notes:

  • Source files and snapshots reference RedirectToTasks (correct).
  • No test/example changes appear necessary for this PR unless you intentionally want to edit historical changelog entries.
packages/vue/package.json (1)

3-3: Minor version bump aligns with API rename

1.11.0 is appropriate for the RedirectToTask → RedirectToTasks rename documented in the changelog.

packages/nextjs/package.json (2)

3-3: Semver minor is appropriate; peer range looks consistent

  • 6.31.0 matches the public API rename noted in release notes.
  • Dev dependency [email protected] satisfies the peer range "^13.5.7 || ^14.2.25 || ^15.2.3".

3-3: Verified — rename + setActive navigate param look good; no changes required in nextjs package

Short check summary:

  • No code references to the old RedirectToTask remain in the Next.js package (only historical mentions in CHANGELOGs/snapshots).
  • @clerk/types exposes the optional navigate param on SetActiveParams.
  • Next.js wrappers do not call clerk.setActive(), so there's nothing to update in the nextjs package itself.

Relevant locations:

  • RedirectToTasks export (correct): packages/nextjs/src/client-boundary/controlComponents.ts
  • Historical mentions only (CHANGELOGs / snapshots): packages/nextjs/CHANGELOG.md, other package CHANGELOGs and snapshots
  • SetActive navigate type: packages/types/src/clerk.ts (SetActiveParams includes navigate?: SetActiveNavigate)
  • Next.js provider navigation mappings (routerPush/routerReplace → internal navigate): packages/nextjs/src/pages/ClerkProvider.tsx and app-router client files

Recommendation (optional):

  • Add integration tests for RedirectToTasks behavior (client + server) and for setActive navigate invocation order. I can draft a Vitest + Next test harness if you want.
packages/agent-toolkit/package.json (2)

3-3: Patch bump is appropriate for dependency updates

0.1.21 aligns with patch-level dependency bumps; no API surface change indicated here.


3-3: Confirmed: internal deps and CHANGELOG entry for 0.1.21

Verified that the package versions match the release notes and the changelog contains the release header.

  • packages/types/package.json — version: 4.77.0
  • packages/shared/package.json — version: 3.20.1
  • packages/backend/package.json — version: 2.8.1
  • packages/agent-toolkit/package.json — version: 0.1.21
  • packages/agent-toolkit/CHANGELOG.md — contains header "## 0.1.21" (line 3)

"version": "0.1.21",

packages/react-router/package.json (1)

3-3: Minor bump aligns with exported component rename

1.9.0 is consistent with the RedirectToTask → RedirectToTasks rename and dependency updates.

packages/testing/package.json (2)

3-3: Semver patch bump looks correct and scoped.

Version advanced to 1.10.14 with no other manifest changes. Namespace, location under packages/, and workspace dependency strategy remain consistent.


3-3: Confirmed: packages/testing is under @clerk and CHANGELOG contains 1.10.14

  • packages/testing/package.json — name: @clerk/testing; version: 1.10.14
  • packages/testing/CHANGELOG.md — contains header ## 1.10.14 (line 3)

No changes required.

packages/themes/package.json (2)

3-3: Patch version bump is appropriate.

2.4.8 -> 2.4.9 aligns with dependency-only changes. Manifest and exports remain unchanged.


3-3: CHANGELOG entry present for packages/themes v2.4.9 — no action needed

Verified: packages/themes/CHANGELOG.md contains "## 2.4.9" (line 3).

packages/shared/package.json (1)

3-3: Shared utils package patch bump looks good.

3.20.0 -> 3.20.1 matches the stated dependency updates; no export map or scripts changes.

packages/astro/package.json (2)

3-3: Astro adapter patch bump approved.

2.11.2 reflects dependency updates only. Type/module/exports remain consistent; peer range for astro is unchanged and compatible.


98-102: No action needed — devDependency astro@^5.12.8 satisfies the peer range ^4.15.0 || ^5.0.0

Verified: packages/astro/package.json shows devDependencies.astro = ^5.12.8 and peerDependencies.astro = ^4.15.0 || ^5.0.0; ^5.12.8 falls into the ^5.0.0 arm of the peer range.

  • File: packages/astro/package.json (lines 98–102)
packages/backend/package.json (2)

3-3: Backend SDK patch bump looks good.

2.8.1 with no manifest/exports changes matches a dependency-only release.


88-110: Confirm CI runs tests across node, edge-runtime, and miniflare targets

I verified packages/backend/package.json defines the test scripts and they target the expected vitest environments — please run them in CI to confirm there are no runtime-specific regressions.

  • packages/backend/package.json
    • test: run-s test:node test:edge-runtime test:cloudflare-miniflare
    • test:node: vitest run --environment node
    • test:edge-runtime: vitest run --environment edge-runtime
    • test:cloudflare-miniflare: vitest run --environment miniflare
packages/clerk-js/package.json (2)

3-3: Semver bump to 5.84.0 looks correct and aligns with the changelog.
Matches the minor API addition (navigate param in setActive). No other metadata changes needed.


3-3: No action required — setActive({ navigate }) is present in types, docs, and tests

Verified the new API is wired up:

  • packages/clerk-js/CHANGELOG.md — 5.84.0 entry mentions adding navigate to clerk.setActive().
  • packages/types/src/clerk.ts — navigate appears in the setActive type and examples (e.g., navigate: CustomNavigation; and example usage).
  • packages/clerk-js/src/core/clerk.ts — setActive accepts/destructures navigate (navigate: setActiveNavigate).
  • packages/clerk-js/src/core/tests/clerk.test.ts — tests call setActive with a navigate argument (multiple occurrences).
  • Numerous UI components and their tests call setActive({ navigate: async ({ session }) => { ... } }) (e.g., SignIn/SignUp components, OrganizationSwitcher, UserButton).

Everything the original comment asked to verify (changelog, types, docs/examples, and tests) is present.

packages/fastify/package.json (2)

3-3: Semver patch bump to 2.4.20 is consistent with dependency-only changes.
Metadata and exports remain unchanged; looks good.


75-83: Engine and peer ranges OK — docs already state Node >=20 for Fastify v5

Verified that docs reflect the Node 20+ requirement and Fastify v5 support.

  • packages/fastify/README.md: line 35 — "Node.js >=20.0.0 or later"
  • packages/fastify/CHANGELOG.md: line 1036 — "In order to support Fastify v5 ... Node.js requirement is now >=20"
packages/react/package.json (1)

3-3: Version bump to 5.42.0 aligns with the RedirectToTasks rename (minor).
Package metadata is consistent; no further changes required here.

packages/express/package.json (1)

3-3: Patch bump to 1.7.20 is consistent with dependency updates only.
No API surface or metadata adjustments needed.

packages/remix/package.json (2)

3-3: Minor bump to 4.11.0 matches the RedirectToTasks rename and dependency updates.
No additional package.json changes needed.


79-86: Remix: RedirectToTasks rename confirmed — react-router peer unchanged

Changelog and export snapshot show the rename to RedirectToTasks; Remix still peers on react-router ^6 and README notes v7 incompatibility. No action required.

  • packages/remix/CHANGELOG.md — contains the rename entry (4.11.0).
  • packages/remix/src/tests/snapshots/exports.test.ts.snap — exports list includes "RedirectToTasks".
  • packages/remix/package.json — version 4.11.0; peerDependencies: "react-router": "^6.0.0".
  • packages/remix/README.md — warns about React Router v7 and points users to @clerk/react-router.
packages/elements/package.json (1)

3-3: Patch bump is appropriate; no issues spotted.

0.23.52 -> 0.23.53 aligns with dependency-only updates. Package metadata, exports, and peer ranges look consistent and follow semantic versioning.

packages/expo-passkeys/package.json (1)

3-3: Version bump LGTM.

0.3.29 -> 0.3.30 as a patch release matches the changelog’s dependency updates. No changes to API surface, scripts, or peer ranges.

packages/localizations/package.json (1)

3-3: Patch release bump looks good.

3.21.0 -> 3.21.1 is consistent with documentation-only updates and internal dependency alignment.

packages/nuxt/package.json (2)

3-3: Nuxt package version bump is consistent with dependent updates.

1.8.5 -> 1.8.6 as a patch bump is appropriate. No other metadata changes observed.


3-3: No lingering RedirectToTask usages in code — only CHANGELOG entries remain

Quick check with ripgrep shows only mentions inside CHANGELOG.md files (changelog notes about the rename/introduction); no code imports/usages or string references were found.

Files with matches:

  • packages/vue/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md

No action required — rename coverage looks consistent across the codebase.

packages/fastify/CHANGELOG.md (1)

3-10: Changelog entry looks correct and semver-appropriate.

Patch release with dependency bumps only; commit references included. No concerns.

packages/astro/CHANGELOG.md (1)

3-10: Solid patch changelog entry.

Dependency versions and linked commits are consistent with the PR objectives. Good to go.

packages/expo/package.json (2)

3-3: Version bump is appropriate for dependency-only changes.

No other manifest fields changed; aligns with semver and repo conventions.


1-126: Verified: package.json versions match topmost CHANGELOG headings for touched packages

Ran the provided script — all packages match their CHANGELOG top headings.

  • packages/expo — 2.14.19
  • packages/chrome-extension — 2.5.20
  • packages/fastify — 2.4.20
  • packages/astro — 2.11.2
  • packages/expo-passkeys — 0.3.30

No changes required.

packages/expo-passkeys/CHANGELOG.md (1)

3-10: Changelog entry is consistent and minimal, as expected for a patch.

Dependency bumps to @clerk/types and @clerk/shared with commit references are correct.

packages/chrome-extension/package.json (1)

3-3: Package version updated correctly for a patch release.

No additional manifest changes; aligns with changeset automation.

packages/types/package.json (2)

3-3: Semver bump looks correct; no issues found.

Patch aligns with repo-wide dependency updates and engines/publishConfig remain consistent.


3-3: No action needed — rename and setActive.navigate are present and exported

Short summary: I verified there are no stale references to RedirectToTask and the optional navigate parameter for clerk.setActive() is declared and exported from the types package.

  • No exact matches for "RedirectToTask" remain; the new "RedirectToTasks" is used across SDKs (examples: packages/react/src/components/controlComponents.tsx, packages/vue/src/components/controlComponents.ts, packages/nextjs/src/client-boundary/controlComponents.ts, and snapshot/CHANGELOG entries).
  • packages/types/src/clerk.ts defines SetActiveNavigate and includes navigate?: SetActiveNavigate inside SetActiveParams; SetActive is exported (SetActive = (setActiveParams: SetActiveParams) => Promise).
  • packages/types/src/index.ts re-exports './clerk', so the SetActive types will be exported from the package root.
  • packages/types/dist is not present locally (expected — CI builds will produce dist/index.d.ts referenced by package.json).
packages/themes/CHANGELOG.md (1)

3-9: Confirmed: CHANGELOG and package.json versions match (2.4.9)

Verified:

  • packages/themes/CHANGELOG.md — header "## 2.4.9" and notes dependency bump to @clerk/[email protected]
  • packages/themes/package.json — "version": "2.4.9" (dependencies show "@clerk/types": "workspace:^")

No further changes required.

packages/agent-toolkit/CHANGELOG.md (1)

3-11: Action: Changelog lists dependency bumps; package.json uses workspace:^ — please verify workspace package versions

CHANGELOG 0.1.21 documents @clerk/[email protected], @clerk/[email protected], @clerk/[email protected]. package.json version matches (0.1.21) but the three deps are declared as "workspace:^" rather than explicit ranges.

Files to check:

  • packages/agent-toolkit/CHANGELOG.md — 0.1.21 lists:
  • packages/agent-toolkit/package.json — version: 0.1.21; dependencies:
    • "@clerk/types": "workspace:^"
    • "@clerk/shared": "workspace:^"
    • "@clerk/backend": "workspace:^"

Requested action: confirm the workspace packages for @clerk/types, @clerk/shared and @clerk/backend have been bumped to the versions in the changelog, or update dependency ranges in package.json to the explicit ^X.Y.Z values if you intended explicit ranges.

packages/localizations/CHANGELOG.md (1)

3-9: Patch entry OK — package.json version matches, but exports are root-only; please verify locale subpath exports.

  • CHANGELOG (packages/localizations/CHANGELOG.md) contains 3.21.1 and references @clerk/[email protected].
  • packages/localizations/package.json version = 3.21.1.
  • package.json exports keys found: ".", "./*", "./package.json" — no locale-specific subpath exports (e.g., "en-US") were present.

Please confirm whether locale subpath exports are intentionally omitted (handled via wildcard/ files array) or if explicit subpath exports should be added/kept.

packages/express/CHANGELOG.md (1)

3-11: Changelog entry looks correct and consistent.

packages/expo/CHANGELOG.md (1)

3-12: Expo changelog entry is accurate and in line with the release train.

packages/chrome-extension/CHANGELOG.md (1)

3-11: LGTM: 2.5.20 entry accurately reflects the dependency bumps

packages/backend/CHANGELOG.md (1)

3-10: LGTM: 2.8.1 entry correctly documents patch dependency updates

packages/nextjs/CHANGELOG.md (1)

11-15: Dependency bumps: looks consistent with the release wave. Add a quick tests note.

The versions align with the repo-wide bumps. Since this change affects a public export, consider adding a lightweight test (or example CI check) that imports RedirectToTasks from each framework wrapper to guard against regressions.

packages/vue/CHANGELOG.md (1)

3-14: Changelog entry looks correct and consistent.

Version, scope (Minor + Patch), links, and dependency bumps are in line with the PR objectives and other packages. Formatting is clean.

packages/nuxt/CHANGELOG.md (2)

3-12: Nuxt patch changelog entry is accurate.

Dependency versions align with the broader release train; formatting and links look good.


3-12: CHANGELOG heading matches package.json (1.8.6) — optional: add dependency-only note

package.json version 1.8.6 matches the changelog heading at packages/nuxt/CHANGELOG.md:3.

  • Optional suggestion: add a one-liner under "## 1.8.6" to clarify impact for consumers.

Suggested insertion:

## 1.8.6

This is a dependency-only release; no code changes for @clerk/nuxt consumers.

### Patch Changes

- Updated dependencies [[`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27)]:
  - @clerk/[email protected]
  - @clerk/[email protected]
  - @clerk/[email protected]
  - @clerk/[email protected]
packages/tanstack-react-start/CHANGELOG.md (1)

3-16: Changelog entry reads well and matches cross-package updates.

Rename and dependency bumps are consistent with other packages in this release.

packages/react-router/CHANGELOG.md (1)

3-16: Entry is clear and consistent.

The Minor rename and Patch dependency bumps align with the rest of the release and are properly linked.

packages/react/CHANGELOG.md (1)

11-13: Dependencies and versions look correct.

The dependency bumps to @clerk/[email protected] and @clerk/[email protected] align with the PR objectives.

packages/clerk-js/CHANGELOG.md (1)

26-31: Versions verified — no action required

All dependency versions listed in packages/clerk-js/CHANGELOG.md match the corresponding package.json and changelogs:

  • packages/clerk-js/package.json — 5.84.0
  • packages/types/package.json — 4.77.0 (packages/types/CHANGELOG.md contains "## 4.77.0")
  • packages/shared/package.json — 3.20.1 (packages/shared/CHANGELOG.md contains "## 3.20.1")
  • packages/localizations/package.json — 3.21.1 (packages/localizations/CHANGELOG.md contains "## 3.21.1")

Also confirmed "navigate" references appear in packages/types changelog and source (no mismatch found).

📝 Walkthrough

Walkthrough

This PR removes three changeset files and adds changelog entries plus version bumps across multiple packages. It introduces two public API updates: an optional navigate callback parameter to clerk.setActive() (@clerk/clerk-js, reflected in @clerk/types) and a rename of RedirectToTask to RedirectToTasks across React, Next.js, Remix, Vue, and TanStack React Start. It also documents a patch in @clerk/shared to invalidate organization memberships based on client user. Most other changes are dependency updates and metadata-only version increments.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested labels

types, clerk-js, nextjs, react, remix, backend, react-router, tanstack, vue, agent-toolkit, astro, chrome-extension, elements, expo, localizations, express, testing, themes, nuxt

Suggested reviewers

  • panteliselef

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

coderabbitai bot commented Aug 13, 2025

Caution

Review failed

The head commit changed during the review from 536126e to 400317a.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

coderabbitai bot commented Aug 13, 2025

Caution

Review failed

Failed to post review comments.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69498df and 536126e.

📒 Files selected for processing (47)
  • .changeset/rich-donuts-agree.md (0 hunks)
  • .changeset/upset-sides-kneel.md (0 hunks)
  • .changeset/warm-rocks-flow.md (0 hunks)
  • packages/agent-toolkit/CHANGELOG.md (1 hunks)
  • packages/agent-toolkit/package.json (1 hunks)
  • packages/astro/CHANGELOG.md (1 hunks)
  • packages/astro/package.json (1 hunks)
  • packages/backend/CHANGELOG.md (1 hunks)
  • packages/backend/package.json (1 hunks)
  • packages/chrome-extension/CHANGELOG.md (1 hunks)
  • packages/chrome-extension/package.json (1 hunks)
  • packages/clerk-js/CHANGELOG.md (1 hunks)
  • packages/clerk-js/package.json (1 hunks)
  • packages/elements/CHANGELOG.md (1 hunks)
  • packages/elements/package.json (1 hunks)
  • packages/expo-passkeys/CHANGELOG.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
  • packages/expo/CHANGELOG.md (1 hunks)
  • packages/expo/package.json (1 hunks)
  • packages/express/CHANGELOG.md (1 hunks)
  • packages/express/package.json (1 hunks)
  • packages/fastify/CHANGELOG.md (1 hunks)
  • packages/fastify/package.json (1 hunks)
  • packages/localizations/CHANGELOG.md (1 hunks)
  • packages/localizations/package.json (1 hunks)
  • packages/nextjs/CHANGELOG.md (1 hunks)
  • packages/nextjs/package.json (1 hunks)
  • packages/nuxt/CHANGELOG.md (1 hunks)
  • packages/nuxt/package.json (1 hunks)
  • packages/react-router/CHANGELOG.md (1 hunks)
  • packages/react-router/package.json (1 hunks)
  • packages/react/CHANGELOG.md (1 hunks)
  • packages/react/package.json (1 hunks)
  • packages/remix/CHANGELOG.md (1 hunks)
  • packages/remix/package.json (1 hunks)
  • packages/shared/CHANGELOG.md (1 hunks)
  • packages/shared/package.json (1 hunks)
  • packages/tanstack-react-start/CHANGELOG.md (1 hunks)
  • packages/tanstack-react-start/package.json (1 hunks)
  • packages/testing/CHANGELOG.md (1 hunks)
  • packages/testing/package.json (1 hunks)
  • packages/themes/CHANGELOG.md (1 hunks)
  • packages/themes/package.json (1 hunks)
  • packages/types/CHANGELOG.md (1 hunks)
  • packages/types/package.json (1 hunks)
  • packages/vue/CHANGELOG.md (1 hunks)
  • packages/vue/package.json (1 hunks)
💤 Files with no reviewable changes (3)
  • .changeset/upset-sides-kneel.md
  • .changeset/warm-rocks-flow.md
  • .changeset/rich-donuts-agree.md
🧰 Additional context used
📓 Path-based instructions (5)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/testing/package.json
  • packages/clerk-js/package.json
  • packages/nuxt/package.json
  • packages/fastify/package.json
  • packages/types/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/backend/package.json
  • packages/nextjs/package.json
  • packages/remix/package.json
  • packages/express/package.json
  • packages/shared/package.json
  • packages/agent-toolkit/package.json
  • packages/expo-passkeys/package.json
  • packages/testing/CHANGELOG.md
  • packages/tanstack-react-start/package.json
  • packages/chrome-extension/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/react-router/package.json
  • packages/react/package.json
  • packages/chrome-extension/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/themes/package.json
  • packages/elements/package.json
  • packages/astro/CHANGELOG.md
  • packages/localizations/package.json
  • packages/localizations/CHANGELOG.md
  • packages/expo/package.json
  • packages/vue/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
packages/*/package.json

📄 CodeRabbit Inference Engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/testing/package.json
  • packages/clerk-js/package.json
  • packages/nuxt/package.json
  • packages/fastify/package.json
  • packages/types/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/backend/package.json
  • packages/nextjs/package.json
  • packages/remix/package.json
  • packages/express/package.json
  • packages/shared/package.json
  • packages/agent-toolkit/package.json
  • packages/expo-passkeys/package.json
  • packages/tanstack-react-start/package.json
  • packages/chrome-extension/package.json
  • packages/react-router/package.json
  • packages/react/package.json
  • packages/themes/package.json
  • packages/elements/package.json
  • packages/localizations/package.json
  • packages/expo/package.json
**/*

⚙️ CodeRabbit Configuration File

If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.

Files:

  • packages/testing/package.json
  • packages/clerk-js/package.json
  • packages/nuxt/package.json
  • packages/fastify/package.json
  • packages/types/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/backend/package.json
  • packages/nextjs/package.json
  • packages/remix/package.json
  • packages/express/package.json
  • packages/shared/package.json
  • packages/agent-toolkit/package.json
  • packages/expo-passkeys/package.json
  • packages/testing/CHANGELOG.md
  • packages/tanstack-react-start/package.json
  • packages/chrome-extension/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/react-router/package.json
  • packages/react/package.json
  • packages/chrome-extension/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/themes/package.json
  • packages/elements/package.json
  • packages/astro/CHANGELOG.md
  • packages/localizations/package.json
  • packages/localizations/CHANGELOG.md
  • packages/expo/package.json
  • packages/vue/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
packages/**/CHANGELOG.md

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Maintain detailed changelogs

Files:

  • packages/testing/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
packages/localizations/**/*

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Localization files must be placed in 'packages/localizations/'.

Files:

  • packages/localizations/package.json
  • packages/localizations/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (generic, chrome)
🔇 Additional comments (45)
packages/fastify/package.json (1)

3-3: LGTM — semver patch bump confirmed: packages/fastify v2.4.20

package.json and CHANGELOG.md both list 2.4.20; the patch bump is appropriate for dependency updates.

Files checked:

  • packages/fastify/package.json — "version": "2.4.20"
  • packages/fastify/CHANGELOG.md — top entry "## 2.4.20"
packages/fastify/CHANGELOG.md (1)

3-11: Changelog entry is clear and consistent with dependency updates — LGTM

The 2.4.20 section accurately documents patch-level dependency bumps and includes precise commit references.

packages/types/package.json (1)

3-3: Approve: [email protected] version bump — verification passed.

Semver is correct for an additive types change; package fields (name/namespace, publishConfig, engines) look consistent. Verification results below.

  • CHANGELOG entries present for:
    • packages/types — 4.77.0
    • packages/chrome-extension — 2.5.20
    • packages/astro — 2.11.2
    • packages/agent-toolkit — 0.1.21
    • packages/nuxt — 1.8.6
  • No lingering singular "RedirectToTask" references outside CHANGELOGs.
  • Plural "RedirectToTasks" occurrences (expected) found in:
    • packages/vue/src/components/controlComponents.ts
    • packages/react/src/components/controlComponents.tsx
    • packages/react/src/components/index.ts
    • packages/nextjs/src/client-boundary/controlComponents.ts
    • several snapshot tests (packages/*/tests/**/exports.test.ts.snap)
  • Many occurrences of setActive(...) were surfaced across code, docs and tests (representative files: packages/clerk-js/src/core/clerk.ts, packages/clerk-js/src/core/tests/clerk.test.ts, packages/clerk-js/src/core/modules/checkout/instance.ts, packages/types/src/clerk.ts, various CHANGELOGs). These are non-blocking but worth a quick eyeball to confirm callers adopt the new navigate parameter where intended.

Snippet (unchanged):
"version": "4.77.0",

LGTM.

packages/chrome-extension/package.json (1)

3-3: Patch bump to 2.5.20 is appropriate for dependency updates; LGTM.
Namespace, files/exports, and workspace dependency strategy look correct.

packages/astro/package.json (1)

3-3: Patch bump to 2.11.2 aligns with dependency updates; LGTM.
Peer range already supports Astro v4 and v5; no issues spotted.

packages/agent-toolkit/package.json (1)

3-3: Confirm Node engine >=20 requirement is intentional.
Most packages in the repo target Node >=18.17.0; this package pins >=20. If intentional due to runtime or dependency needs, all good—otherwise consider aligning to the repo baseline for consistency.

packages/nuxt/package.json (1)

3-3: Patch bump to 1.8.6 looks correct; LGTM.
Exports, files, and peer dependency ranges remain consistent.

packages/vue/package.json (1)

3-3: Semver bump to 1.11.0 looks correct for the public Rename (minor).

Version aligns with the RedirectToTask → RedirectToTasks rename called out in the changelog. Package metadata and export map remain unchanged and consistent.

packages/expo/package.json (2)

3-3: Patch bump to 2.14.19 is consistent with dependency updates.

No API surface changes observed in package.json; exports and peer ranges remain stable.


3-3: Sanity-check — no code-level references found; only changelog mentions

Quick rg scan for RedirectToTask and setActive in packages/expo found no usages in code. The only matches are documentation entries in:

  • packages/expo/CHANGELOG.md:1272, 2021, 2830, 3030

Conclusion: no code changes required in Expo for the bumped Clerk libs based on this scan. Run integration/e2e checks if you want runtime confirmation.

packages/localizations/package.json (2)

3-3: Patch bump to 3.21.1 is appropriate and complies with localization packaging rules.

Files remain under packages/localizations and exports unchanged.


3-3: Action required — possible localization ↔ types mismatch; please run generator & lint

Quick check I ran against the repo shows a potential mismatch between the type definition and the localizations:

  • packages/types/src/localization.ts (__internal_LocalizationResource) — ~802 keys (type-defined)
  • packages/localizations/src/en-US.ts — parsed only 4 top-level entries by my quick parser, producing ~798 “missing” nested keys (this extraction may be brittle due to nested templates/strings)

Please verify manually and re-run the localization generator/linter (CI) to ensure keys are synced. Files to check:

  • packages/types/src/localization.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/utils/generate.ts
  • packages/localizations/package.json (scripts -> "generate", "lint")

Suggested steps:

  • Run the package generator and format step locally: pnpm -w --filter @clerk/localizations run generate
  • Lint the package: pnpm -w --filter @clerk/localizations run lint
  • Inspect and commit any generated changes, then ensure CI passes

I couldn't conclusively auto-verify because the object extraction/parsing can be thrown off by template strings; please run the above and confirm there are no missing/unused localization keys.

packages/testing/package.json (2)

3-3: Patch bump to 1.10.14 aligns with internal deps updates.

Exports and peer ranges for Playwright/Cypress remain unchanged and sensible.


3-3: No E2E fixtures reference RedirectToTask; rename to RedirectToTasks is already applied — consider adding smoke tests

Searched the repo for RedirectToTask/RedirectToTasks. Only historical mentions of RedirectToTask appear in changelogs; code and snapshots use RedirectToTasks.

Files of interest:

  • packages/react/src/components/controlComponents.tsx (export RedirectToTasks)
  • packages/vue/src/components/controlComponents.ts (export RedirectToTasks)
  • packages/nextjs/src/client-boundary/controlComponents.ts (includes RedirectToTasks)
  • snapshots/tests updated: packages/tanstack-react-start/src/tests/snapshots/exports.test.ts.snap, packages/remix/src/tests/snapshots/exports.test.ts.snap
  • changelogs with historical mentions: packages/*/CHANGELOG.md

No E2E fixture updates appear necessary. Still recommended: add a small smoke test in example apps to cover the renamed RedirectToTasks component to prevent regressions.

packages/nextjs/package.json (2)

3-3: Minor bump to 6.31.0 tracks the public rename and dependency bumps.

Manifest structure, export map, and peer ranges look consistent.


3-3: Verification complete — RedirectToTask rename & setActive(navigate?) validated

Short summary:

  • No remaining imports/usages of the old RedirectToTask in source files (only historical mentions in CHANGELOGs).
  • The new setActive navigate option is present in the types, implemented in clerk-js, and exercised by unit tests.

Key locations:

  • packages/types/src/clerk.ts — SetActiveParams includes navigate?: SetActiveNavigate; export type SetActiveNavigate = ({ session }: { session: SessionResource }) => Promise<unknown>;
  • packages/clerk-js/src/core/clerk.ts — setActive destructures/uses the navigate param and the file defines an internal setActiveNavigate helper used by sign-in/sign-up flows.
  • packages/clerk-js/src/core/tests/clerk.test.ts — tests call setActive(..., navigate) and assert the navigate callback is invoked.
  • RedirectToTasks (new name) appears in source at:
    • packages/react/src/components/controlComponents.tsx
    • packages/nextjs/src/client-boundary/controlComponents.ts
    • packages/vue/src/components/controlComponents.ts
    • snapshots: packages/tanstack-react-start/src/tests/snapshots/exports.test.ts.snap, packages/react-router/src/tests/snapshots/exports.test.ts.snap

Conclusion:

  • No fixes required from this review. If you want broader test coverage for the new navigate callback or a follow-up issue to add targeted tests, I can open one on request.
packages/expo-passkeys/package.json (1)

3-3: Semver patch bump looks correct for dependency-only updates.
No API surface changes here; version 0.3.30 aligns with CHANGELOG and monorepo baseline bumps.

packages/tanstack-react-start/package.json (2)

3-3: Minor version bump is appropriate for the RedirectToTask → RedirectToTasks rename.
Semver minor is correct for a public component rename; dependencies are workspace-pinned and will resolve to the updated versions.


56-70: Verified — RedirectToTask renamed to RedirectToTasks in this package; tests updated

Searched the repo for both names. For packages/tanstack-react-start there are no stale source imports/usages of the old singular name and tests/snapshots assert the new export.

Files of note:

  • packages/tanstack-react-start/src/tests/snapshots/exports.test.ts.snap — contains "RedirectToTasks"
  • packages/tanstack-react-start/CHANGELOG.md — documents the rename (informational)

No further action required.

packages/express/package.json (1)

3-3: Patch bump is consistent with internal dependency updates.
No API/export changes; peer range for express and Node engine constraints remain appropriate.

packages/themes/package.json (1)

3-3: Patch bump aligns with @clerk/types update.
No changes to exports; shadcn.css subpath remains intact. Looks good.

packages/backend/package.json (1)

3-3: Patch bump acknowledged — confirm built exports/types for Machine and M2MToken.

Source verification:

  • packages/backend/src/index.ts (lines 129–130) — exports include Machine and M2MToken.
  • packages/backend/src/api/resources/index.ts — re-exports ./Machine and ./M2MToken.
  • packages/backend/dist/index.* and packages/backend/dist/index.d.ts — missing from repo; I couldn't verify generated JS/DTs or package entry.

Please run the package build and confirm that packages/backend/dist/index(.js/.d.ts) exposes Machine and M2MToken and that package.json's main/types/exports point to the generated entry so those symbols are surfaced to consumers.

packages/react/package.json (1)

3-3: Version bump & rename verified — no code references to RedirectToTask remain

  • packages/react/CHANGELOG.md contains a 5.42.0 entry: "Rename RedirectToTask control component to RedirectToTasks".
  • Repo scan (excluding CHANGELOGs) shows no occurrences of the old singular name in code; the only remaining mentions of "RedirectToTask" are historical entries in CHANGELOGs:
    • packages/vue/CHANGELOG.md (line ~65)
    • packages/react/CHANGELOG.md (line ~81)
    • packages/nextjs/CHANGELOG.md (line ~113)
  • Code and exports reference the new name (examples): packages/react/src/components/controlComponents.tsx, packages/react/src/components/index.ts, packages/vue/src/components/controlComponents.ts, packages/nextjs/src/client-boundary/controlComponents.ts and related snapshot tests.

Result: no fixes required — changelog documents the rename and code uses RedirectToTasks.

packages/expo-passkeys/CHANGELOG.md (1)

3-10: Changelog entry is consistent and scoped as patch; no issues.

Entry 0.3.30 clearly lists internal dependency updates only. No action required.

packages/vue/CHANGELOG.md (1)

3-14: Minor release entry is clear — verified no remaining code references to RedirectToTask

  • Verified packages/vue package.json version matches CHANGELOG top entry (1.11.0).
  • Searched packages/vue and packages/nuxt for usages/imports of RedirectToTask — none found.
  • Remaining occurrence: packages/vue/CHANGELOG.md:65 — historical entry "Introduce <RedirectToTask />" (no action required).
packages/chrome-extension/CHANGELOG.md (1)

3-11: Changelog patch is consistent with dependency bumps; no functional changes noted.

Entry 2.5.20 correctly lists dependent version updates. Looks good.

packages/react-router/package.json (1)

3-3: Version bump to 1.9.0 — changelog updated and no lingering RedirectToTask usages in packages/react-router

Verified results:

  • packages/react-router/CHANGELOG.md contains a "## 1.9.0" entry documenting "Rename RedirectToTask control component to RedirectToTasks" and the dependency bumps.
  • No remaining occurrences of "RedirectToTask" (JSX or imports) found in packages/react-router source or tests (searched for 'RedirectToTask', '<RedirectToTask' and import patterns).
  • Repo-wide hits for "RedirectToTask" are only historical changelog mentions in other packages (e.g., packages/vue/CHANGELOG.md, packages/react/CHANGELOG.md, packages/nextjs/CHANGELOG.md); code exports/snapshots reference the correct "RedirectToTasks".

No changes required here.

packages/clerk-js/package.json (1)

3-3: Approve: semver minor bump is correct — changelog documents setActive navigate

Changelog contains a 5.84.0 entry that adds the optional navigate parameter to clerk.setActive(), so the minor version bump is appropriate. LGTM.

  • packages/clerk-js/package.json — "version": "5.84.0"
  • packages/clerk-js/CHANGELOG.md — ## 5.84.0 and "Add navigate parameter to clerk.setActive()" (documented)
  "version": "5.84.0",
packages/shared/package.json (1)

3-3: Patch bump looks correct for internal adjustments and dependency sync.
No API surface indicated here; patch is the right choice.

packages/localizations/CHANGELOG.md (1)

3-9: Changelog verified — package.json and CHANGELOG.md match (3.21.1)

Changelog entry formatting and content look good; patch notes correctly reference @clerk/[email protected].

  • packages/localizations/package.json — version: 3.21.1
  • packages/localizations/CHANGELOG.md — '## 3.21.1' (line 3)
packages/elements/package.json (1)

3-3: Patch bump is consistent with dependency updates only.
No API changes implied; versioning is appropriate.

packages/remix/CHANGELOG.md (2)

3-8: AI summary inconsistency: this entry is not metadata-only.

The AI-generated summary claims no public API changes, but this section explicitly documents a component rename. Treat this as a real, user-facing change.


11-16: Dependency updates look consistent with the repo-wide bump.

The versions for @clerk/types, @clerk/shared, @clerk/clerk-react, and @clerk/backend align with the PR objectives. No issues from a changelog standpoint.

packages/themes/CHANGELOG.md (1)

3-9: Patch entry and dependency bump look good.

The 2.4.9 changelog correctly documents the dependency update to @clerk/[email protected] and aligns with the coordinated release.

packages/elements/CHANGELOG.md (1)

3-11: Changelog & package.json versions verified — approved

Changelog entry 0.23.53 is clear, formatted as expected, and the package.json versions match the changelog.

  • packages/elements/CHANGELOG.md — 0.23.53 (Patch)
  • packages/elements/package.json — 0.23.53
  • packages/testing/package.json — 1.10.14
  • packages/nuxt/package.json — 1.8.6
  • packages/express/package.json — 1.7.20
  • packages/agent-toolkit/package.json — 0.1.21

All good; no changes required.

packages/express/CHANGELOG.md (1)

3-11: Express changelog patch entry looks good.

  • Patch version 1.7.20 with dependency bumps only.
  • References and formatting match prior entries.
packages/agent-toolkit/CHANGELOG.md (1)

3-11: Agent Toolkit changelog entry is correct and consistent.

  • Patch version 0.1.21 with dependency bumps listed.
  • Formatting and link style consistent with the rest of the file.
packages/tanstack-react-start/CHANGELOG.md (1)

9-16: LGTM on dependency bump notes.

The dependency versions and referenced commits look consistent with the broader release. No issues from the changelog perspective.

packages/expo/CHANGELOG.md (2)

3-12: LGTM: Patch release entry is clear and consistent.

Dependency bumps and commit refs align with the repo-wide release. No further changes needed in the changelog.


3-12: Confirm workspace pins + root workspace bumps

packages/expo/package.json version matches the CHANGELOG (2.14.19). However, internal @clerk/* deps are declared as workspace:^ (no exact versions in this manifest) and the peer dep is @clerk/expo-passkeys: >=0.0.6.

Files to check:

  • packages/expo/package.json
    • version: 2.14.19
    • dependencies: @clerk/clerk-js: workspace:^, @clerk/clerk-react: workspace:^, @clerk/shared: workspace:^, @clerk/types: workspace:^
    • peerDependencies: @clerk/expo-passkeys: >=0.0.6
  • packages/expo/CHANGELOG.md — lists updated versions: @clerk/[email protected], @clerk/[email protected], @clerk/[email protected], @clerk/[email protected]

Action required:

  • Verify the root workspace package manifests or the individual @clerk/* package versions have been bumped to the versions referenced in the CHANGELOG. If they have, no change is needed in packages/expo (workspace:^ is expected). If not, update the workspace packages/releases accordingly.
packages/astro/CHANGELOG.md (1)

3-11: Changelog entry looks good

  • Version header, section headings, and dependency bullets are consistent with the project’s convention.
  • Links to commits resolve correctly.
packages/react/CHANGELOG.md (1)

11-13: Dependency bump is consistent

Updated to @clerk/[email protected] and @clerk/[email protected], matching the PR objectives and cross-repo updates.

packages/types/CHANGELOG.md (1)

3-24: Confirm: @clerk/types exposes navigate on setActive

SetActiveParams includes navigate?: SetActiveNavigate and SetActiveNavigate is defined/exported; the types are re-exported from the package index and downstream packages call setActive with navigate, so there is no mismatch.

Files/evidence:

  • packages/types/src/clerk.ts — export type SetActiveNavigate = ({ session }: { session: SessionResource }) => Promise<unknown>; (line ~123) and export type SetActiveParams = { ... navigate?: SetActiveNavigate; } (lines ~1185–1225).
  • packages/types/src/index.ts — re-exports ./clerk.
  • Downstream usages (representative examples showing alignment):
    • packages/clerk-js/src/core/clerk.ts — multiple calls to setActive({ ..., navigate: async ({ session }) => { ... } }) (examples around lines ~1875, 1890, 1941, 1955, 1981, 2193).
    • packages/clerk-js/src/ui/components/* — sign-in / sign-up components use navigate in setActive calls (e.g., SignIn/SignUpStart, various SignIn/SignUp cards).
    • packages/clerk-js/src/core/tests/clerk.test.ts — tests exercising navigate behavior.

Result: types are updated and downstream packages in this repo are aligned. No changes required.

packages/backend/CHANGELOG.md (1)

3-10: Approve — changelog matches package.json; workspace deps are expected

Verified: packages/backend/package.json version = 2.8.1 (matches CHANGELOG). @clerk/types and @clerk/shared are set to "workspace:^" (monorepo workspace references), so the changelog's explicit version numbers are informational and do not require changes.

Files checked:

  • packages/backend/CHANGELOG.md (entry for 2.8.1)
  • packages/backend/package.json — version: 2.8.1; "@clerk/types": "workspace:^"; "@clerk/shared": "workspace:^"
packages/clerk-js/CHANGELOG.md (1)

28-31: Dependency bumps align with the change. LGTM.

The updated versions for @clerk/types, @clerk/shared, and @clerk/localizations match the new API surface.

📝 Walkthrough

Walkthrough

This PR primarily updates package versions and changelogs across multiple packages. It deletes three changeset files. It introduces a public API change adding an optional navigate callback to Clerk.setActive in @clerk/clerk-js/@clerk/types. It documents/propagates a public component rename RedirectToTask to RedirectToTasks across React, Next.js, Remix, Vue, React Router, and TanStack React Start packages. Backend changelog notes dependency bumps, with prior public exports (Machine, M2MToken) referenced. No functional code changes are shown beyond the documented API addition/rename.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • ci(repo): Version packages #6321 — Both PRs touch after-auth navigation in @clerk/clerk-js; this one adds setActive navigate, while that PR refactors after-auth flows.

Suggested reviewers

  • panteliselef
  • jfoshee

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot force-pushed the changeset-release/main branch from 400317a to 8fdc6fb Compare August 13, 2025 22:20
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 10

🧹 Nitpick comments (19)
packages/tanstack-react-start/package.json (1)

3-3: Tests for the renamed component.

No tests were modified in this PR. Please ensure coverage exists for RedirectToTasks across adapters (rendering, navigation, and error paths). I can help sketch quick vitest cases if desired.

packages/testing/package.json (1)

76-81: Ensure test utilities and examples reflect m2m token API changes.

Given backend changes (result.secret → result.token, verifySecret → verifyToken), validate that any helpers, docs, or examples in @clerk/testing are updated and covered by tests.

Would you like me to draft sample Playwright/Cypress snippets demonstrating verifyToken usage and asserting failure paths?

packages/chrome-extension/CHANGELOG.md (1)

3-11: Deduplicate repeated commit reference in 2.5.20 entry.

The commit 69498df appears twice in the same bullet list. Consider removing the duplicate to keep the entry clean.

Apply this minimal diff within the commit list:

- - Updated dependencies [[`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27)]:
+ - Updated dependencies [[`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
packages/remix/CHANGELOG.md (2)

7-8: Include a short migration snippet for the component rename

A small before/after code snippet will help users adopt RedirectToTasks quickly.

For example:

// Before
import { RedirectToTask } from '@clerk/remix';

// After
import { RedirectToTasks } from '@clerk/remix';

11-16: Deduplicate commit references in dependency updates

69498df is listed twice in the bracketed commit list. Suggest removing the duplicate for cleanliness.

Apply this diff:

- - Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27)]:
+ - Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
packages/elements/CHANGELOG.md (1)

3-11: Changelog entry looks good; minor nit: duplicate commit hash in dependency note

The patch entry is clear and consistent. One small nit: the commit reference 69498df appears twice in the same bullet list.

Apply this diff to deduplicate the commit reference:

- - Updated dependencies [[`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27)]:
+ - Updated dependencies [[`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
packages/express/CHANGELOG.md (1)

3-11: Consider adding a short note about downstream m2m token rename

Since this package now depends on @clerk/[email protected], it may help consumers to know about the backend’s m2m response change (secret → token) and deprecation of verifySecret in favor of verifyToken, even though there’s no API change in express itself. A one-liner under Patch Changes can prevent surprises for users reading only this changelog.

packages/vue/CHANGELOG.md (2)

3-14: Document migration snippet for RedirectToTasks rename

The rename is clear. Consider adding a brief “Migration” snippet to help users update imports/usages quickly.

For example:

- import { RedirectToTask } from '@clerk/vue';
+ import { RedirectToTasks } from '@clerk/vue';

If you’ve kept a temporary alias export for backward compatibility, noting deprecation timing here would also help.


3-14: Add/adjust tests to catch regressions from the rename

There are no tests in this PR. Recommend adding a lightweight unit/integration test to assert RedirectToTasks renders and is exported from the package entry point. If a temporary alias exists, add a deprecation test to ensure it warns properly and will be removed on schedule. I can help scaffold these.

Do you want me to draft a test file and a codemod script to assist consumers with the rename?

packages/shared/CHANGELOG.md (1)

7-8: Consider briefly clarifying end-user impact of the membership invalidation.

A one-liner can help consumers understand whether any action is required (e.g., cache invalidation behavior and whether this could cause extra fetches/UI refreshes).

 - Invalidate organization memberships based on client user ([#6530](https://github.com/clerk/javascript/pull/6530)) by [@iagodahlem](https://github.com/iagodahlem)
+ - Invalidate organization memberships based on client user ([#6530](https://github.com/clerk/javascript/pull/6530)) by [@iagodahlem](https://github.com/iagodahlem)
+   - Note: This is an internal cache invalidation improvement; no code changes are required for consumers beyond taking this version.
packages/react-router/CHANGELOG.md (1)

5-8: Call out deprecation/alias strategy for the renamed component to ease migration.

Explicitly stating whether RedirectToTask is still exported as a temporary alias (and planned removal version) helps consumers plan upgrades.

 ### Minor Changes

-- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+  - If applicable, `RedirectToTask` may be kept as a deprecated alias for a limited period. Prefer `RedirectToTasks`. If an alias is provided, it will be removed in a future minor release; check release notes for timelines.
packages/tanstack-react-start/CHANGELOG.md (1)

5-8: Add a short deprecation guidance for the renamed component.

Aligning with other packages, explicitly tell users what to do and whether a temporary alias exists.

 ### Minor Changes

-- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+  - Migrate imports to `RedirectToTasks`. If a temporary alias is exported for `RedirectToTask`, treat it as deprecated and plan removal in an upcoming minor release.
packages/types/CHANGELOG.md (1)

3-25: Docs/readability: casing consistency for setActive API name

Consider aligning the casing with other entries that reference the Clerk singleton. The bullet currently says clerk.setActive() while most references use Clerk.* when naming the public API in prose. The code example can continue using the lowercase clerk instance.

- - Add `navigate` parameter to `clerk.setActive()` for custom navigation before the session and/or organization is set. ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+ - Add `navigate` parameter to `Clerk.setActive()` for custom navigation before the session and/or organization is set. ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
packages/backend/CHANGELOG.md (2)

7-7: Clarify scope: specify which response removes secret

Minor wording tweak to remove ambiguity. Explicitly calling out the method helps readers understand exactly which response changed.

- - Remove `secret` in favor of `token` in m2m response. ([#6542](https://github.com/clerk/javascript/pull/6542)) by [@wobsoriano](https://github.com/wobsoriano)
+ - Remove the `secret` field in favor of `token` in the `m2mTokens.create()` response. ([#6542](https://github.com/clerk/javascript/pull/6542)) by [@wobsoriano](https://github.com/wobsoriano)

25-25: Fix grammar: “in favor or” → “in favor of”

Small typo in the deprecation note.

- - Deprecates `clerkClient.m2mTokens.verifySecret({ secret: 'mt_xxx' })` in favor or `clerkClient.m2mTokens.verifyToken({ token: 'mt_xxx' })` ([#6536](https://github.com/clerk/javascript/pull/6536)) by [@wobsoriano](https://github.com/wobsoriano)
+ - Deprecates `clerkClient.m2mTokens.verifySecret({ secret: 'mt_xxx' })` in favor of `clerkClient.m2mTokens.verifyToken({ token: 'mt_xxx' })` ([#6536](https://github.com/clerk/javascript/pull/6536)) by [@wobsoriano](https://github.com/wobsoriano)
packages/react/CHANGELOG.md (1)

9-13: Dependency bumps look correct for this release

Updated dependencies align with the PR objectives: @clerk/[email protected] and @clerk/[email protected].

Optional: you could add a brief note if these bumps include any reactive type changes affecting this package’s public API (none apparent here).

packages/clerk-js/CHANGELOG.md (1)

7-24: Add the exact navigate signature and awaiting behavior for clarity

Briefly documenting the callback’s signature and the fact that it’s awaited will help avoid misuse and make the contract explicit.

Apply this diff to insert a short note under the bullet:

 - Add `navigate` parameter to `clerk.setActive()` for custom navigation before the session and/or organization is set. ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+
+  Signature:
+  ```ts
+  navigate?: (ctx: { session: Session }) => void | Promise<void>
+  ```
+
+  Notes:
+  - The `navigate` callback is awaited; throw or reject to surface errors to callers.
+  - Return early after custom navigation if you don’t want to continue default post-activation flows.
packages/nextjs/CHANGELOG.md (2)

7-7: Clarify wording and add a brief migration hint.

"control component" is inconsistent with prior entries (“exported component”). Also, a short migration hint helps users scanning the changelog.

-- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+- Rename `RedirectToTask` exported component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+  Migration: update imports from `RedirectToTask` to `RedirectToTasks`.

11-11: Deduplicate commit references in the “Updated dependencies” line.

The commit 69498df appears twice; keep it once to avoid noise.

- - Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27)]:
+ - Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d400782 and 8fdc6fb.

📒 Files selected for processing (49)
  • .changeset/chatty-kings-raise.md (0 hunks)
  • .changeset/rich-donuts-agree.md (0 hunks)
  • .changeset/small-adults-crash.md (0 hunks)
  • .changeset/upset-sides-kneel.md (0 hunks)
  • .changeset/warm-rocks-flow.md (0 hunks)
  • packages/agent-toolkit/CHANGELOG.md (1 hunks)
  • packages/agent-toolkit/package.json (1 hunks)
  • packages/astro/CHANGELOG.md (1 hunks)
  • packages/astro/package.json (1 hunks)
  • packages/backend/CHANGELOG.md (1 hunks)
  • packages/backend/package.json (1 hunks)
  • packages/chrome-extension/CHANGELOG.md (1 hunks)
  • packages/chrome-extension/package.json (1 hunks)
  • packages/clerk-js/CHANGELOG.md (1 hunks)
  • packages/clerk-js/package.json (1 hunks)
  • packages/elements/CHANGELOG.md (1 hunks)
  • packages/elements/package.json (1 hunks)
  • packages/expo-passkeys/CHANGELOG.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
  • packages/expo/CHANGELOG.md (1 hunks)
  • packages/expo/package.json (1 hunks)
  • packages/express/CHANGELOG.md (1 hunks)
  • packages/express/package.json (1 hunks)
  • packages/fastify/CHANGELOG.md (1 hunks)
  • packages/fastify/package.json (1 hunks)
  • packages/localizations/CHANGELOG.md (1 hunks)
  • packages/localizations/package.json (1 hunks)
  • packages/nextjs/CHANGELOG.md (1 hunks)
  • packages/nextjs/package.json (1 hunks)
  • packages/nuxt/CHANGELOG.md (1 hunks)
  • packages/nuxt/package.json (1 hunks)
  • packages/react-router/CHANGELOG.md (1 hunks)
  • packages/react-router/package.json (1 hunks)
  • packages/react/CHANGELOG.md (1 hunks)
  • packages/react/package.json (1 hunks)
  • packages/remix/CHANGELOG.md (1 hunks)
  • packages/remix/package.json (1 hunks)
  • packages/shared/CHANGELOG.md (1 hunks)
  • packages/shared/package.json (1 hunks)
  • packages/tanstack-react-start/CHANGELOG.md (1 hunks)
  • packages/tanstack-react-start/package.json (1 hunks)
  • packages/testing/CHANGELOG.md (1 hunks)
  • packages/testing/package.json (1 hunks)
  • packages/themes/CHANGELOG.md (1 hunks)
  • packages/themes/package.json (1 hunks)
  • packages/types/CHANGELOG.md (1 hunks)
  • packages/types/package.json (1 hunks)
  • packages/vue/CHANGELOG.md (1 hunks)
  • packages/vue/package.json (1 hunks)
💤 Files with no reviewable changes (5)
  • .changeset/warm-rocks-flow.md
  • .changeset/chatty-kings-raise.md
  • .changeset/small-adults-crash.md
  • .changeset/upset-sides-kneel.md
  • .changeset/rich-donuts-agree.md
🧰 Additional context used
📓 Path-based instructions (5)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/types/package.json
  • packages/nextjs/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/react/package.json
  • packages/expo-passkeys/package.json
  • packages/express/package.json
  • packages/tanstack-react-start/package.json
  • packages/fastify/package.json
  • packages/react-router/package.json
  • packages/elements/package.json
  • packages/clerk-js/package.json
  • packages/vue/package.json
  • packages/testing/package.json
  • packages/fastify/CHANGELOG.md
  • packages/backend/package.json
  • packages/chrome-extension/CHANGELOG.md
  • packages/chrome-extension/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/themes/package.json
  • packages/agent-toolkit/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/agent-toolkit/package.json
  • packages/remix/package.json
  • packages/testing/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/shared/package.json
  • packages/react/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/astro/package.json
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/localizations/package.json
  • packages/types/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/elements/CHANGELOG.md
packages/*/package.json

📄 CodeRabbit Inference Engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

  • packages/types/package.json
  • packages/nextjs/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/react/package.json
  • packages/expo-passkeys/package.json
  • packages/express/package.json
  • packages/tanstack-react-start/package.json
  • packages/fastify/package.json
  • packages/react-router/package.json
  • packages/elements/package.json
  • packages/clerk-js/package.json
  • packages/vue/package.json
  • packages/testing/package.json
  • packages/backend/package.json
  • packages/chrome-extension/package.json
  • packages/themes/package.json
  • packages/agent-toolkit/package.json
  • packages/remix/package.json
  • packages/shared/package.json
  • packages/astro/package.json
  • packages/localizations/package.json
**/*

⚙️ CodeRabbit Configuration File

If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.

Files:

  • packages/types/package.json
  • packages/nextjs/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/react/package.json
  • packages/expo-passkeys/package.json
  • packages/express/package.json
  • packages/tanstack-react-start/package.json
  • packages/fastify/package.json
  • packages/react-router/package.json
  • packages/elements/package.json
  • packages/clerk-js/package.json
  • packages/vue/package.json
  • packages/testing/package.json
  • packages/fastify/CHANGELOG.md
  • packages/backend/package.json
  • packages/chrome-extension/CHANGELOG.md
  • packages/chrome-extension/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/themes/package.json
  • packages/agent-toolkit/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/agent-toolkit/package.json
  • packages/remix/package.json
  • packages/testing/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/shared/package.json
  • packages/react/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/astro/package.json
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/localizations/package.json
  • packages/types/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/elements/CHANGELOG.md
packages/**/CHANGELOG.md

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Maintain detailed changelogs

Files:

  • packages/fastify/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/elements/CHANGELOG.md
packages/localizations/**/*

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Localization files must be placed in 'packages/localizations/'.

Files:

  • packages/localizations/CHANGELOG.md
  • packages/localizations/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (55)
packages/expo/package.json (1)

3-3: Semver patch bump verified — package.json and CHANGELOG.md both show 2.14.19

Confirmed with the provided check: package.json and the top entry in packages/expo/CHANGELOG.md both report 2.14.19.

Files checked:

  • packages/expo/package.json — version: 2.14.19
  • packages/expo/CHANGELOG.md — top entry: 2.14.19

Snippet:

  "version": "2.14.19",
packages/expo/CHANGELOG.md (1)

3-12: Changelog entry is scoped and accurate for a patch release.

  • Clearly documents dependency bumps to @clerk/clerk-js 5.84.0, @clerk/types 4.77.0, @clerk/shared 3.20.1, and @clerk/clerk-react 5.42.0.
  • No runtime notes added, which is appropriate given no code changes in this package.

LGTM.

packages/nuxt/package.json (1)

3-3: Version bump aligns with semantic versioning and repo policies

Patch bump to 1.8.6 is appropriate for dependency updates; package name, scope, location, and publishConfig all comply with guidelines.

packages/types/package.json (1)

3-3: Semver bump looks correct and consistent with PR scope.

Minor bump to 4.77.0 aligns with the new optional navigate parameter in setActive types.

packages/tanstack-react-start/package.json (2)

3-3: Version bump to 0.22.0 is appropriate for the public rename.

Minor bump matches the RedirectToTask → RedirectToTasks rename captured in the changelog.


79-86: Confirm peer ranges remain accurate post-update.

Peers are pinned to ^1.127.0 while devDeps are ^1.128.0. If we rely on APIs introduced in 1.128, consider bumping peers to ^1.128.0 to avoid consumer peer warnings; otherwise, keeping a broader minimum is fine.

packages/astro/package.json (1)

3-3: Patch bump to 2.11.2 is correct for dependency-only changes.

No additional issues spotted; exports and peers look consistent.

packages/testing/package.json (2)

3-3: Patch bump to 1.10.14 aligns with dependency updates.

Looks good.


3-3: Verify deprecated m2m usages (testing + examples) — scan inconclusive (examples missing)

I ran the ripgrep scan. packages/testing: no matches for m2mTokens.verifySecret(...) or result.secret. examples directory was not present in this checkout, so the scan is incomplete.

Files/locations to check:

  • packages/testing — scanned, no matches found.
  • examples — missing (couldn't scan). Please ensure example projects are present or confirm there are none to check.

Run this adjusted script locally (it skips non-existent dirs) and fix any matches by switching to verifyToken({ token }) and result.token:

#!/bin/bash
set -euo pipefail
EXCLUDES=(-g '!.changeset/*' -g '!**/CHANGELOG.md' -g '!**/CHANGELOG.mdx')
TARGETS=(packages/testing)
[ -d examples ] && TARGETS+=(examples)

echo "Scanning ${TARGETS[*]} for deprecated m2m usages..."
rg -n $'m2mTokens\\.verifySecret\\s*\\(' "${TARGETS[@]}" "${EXCLUDES[@]}" || true
rg -n $'result\\.secret\\b' "${TARGETS[@]}" "${EXCLUDES[@]}" || true

echo "If any matches appear above, switch to verifyToken({ token }) and result.token."
packages/themes/package.json (1)

3-3: Patch bump to 2.4.9 is appropriate for types dependency update.

All package metadata and exports look consistent.

packages/remix/package.json (1)

3-3: Version bump to 4.11.0 looks correct and consistent with the changelog.
Aligned with the RedirectToTask → RedirectToTasks rename and dependency bumps described in CHANGELOG.md. Semver minor is appropriate if a deprecated alias remains.

packages/elements/package.json (2)

3-3: Patch version bump to 0.23.53 looks good.
Pure metadata update consistent with repo-wide dependency bumps; no API surface changed in this package.


3-3: Sanity-check passed — changelog entry exists for packages/elements v0.23.53

Found "## 0.23.53" in packages/elements/CHANGELOG.md (line 3). No action required.

  • packages/elements/package.json — version: 0.23.53
  • packages/elements/CHANGELOG.md — contains "## 0.23.53" (line 3)
packages/react-router/package.json (1)

3-3: Version 1.9.0 is appropriate given the documented rename and dependency updates.
Assuming a deprecation alias exists for RedirectToTask, a minor bump is acceptable.

packages/react/package.json (1)

3-3: React package version bump to 5.42.0 LGTM.
Matches the rename and dependency bumps documented in the changelog; no other metadata changes.

packages/clerk-js/package.json (2)

3-3: Clerk.js version bump to 5.84.0 looks good.
This aligns with the new optional navigate parameter addition and dependency bumps.


3-3: Types & tests for setActive({ navigate }) verified — no changes required

Types and tests are present.

  • packages/types/src/clerk.ts — defines SetActiveNavigate and includes navigate?: SetActiveNavigate in SetActiveParams.
  • packages/clerk-js/src/core/tests/clerk.test.ts — contains tests calling setActive({ navigate }) and asserting navigate is invoked (e.g. tests around lines shown in the search output).
  • packages/clerk-js/CHANGELOG.md — documents the new navigate parameter.
packages/fastify/package.json (1)

3-3: Patch bump to 2.4.20 — aligned with dependency updates (LGTM).

No export or runtime changes. Peer dep (fastify >=5) aligns with devDependency. Nothing else to do here.

packages/agent-toolkit/package.json (1)

3-3: Patch bump to 0.1.21 — consistent with backend/types/shared updates (LGTM).

Metadata, exports, and bin remain unchanged. Good to ship.

packages/nextjs/package.json (1)

3-3: Approve: bump to 6.31.0 — RedirectToTask → RedirectToTasks rename verified

Changelog and repo checks passed: packages/nextjs/CHANGELOG.md contains a "## 6.31.0" entry mentioning RedirectToTasks, and no stale RedirectToTask references were found.

  • packages/nextjs/package.json — "version": "6.31.0"
  • packages/nextjs/CHANGELOG.md — contains the rename entry
  • Repository search — no occurrences of "RedirectToTask"

Optional: consider adding a minimal type-level test asserting RedirectToTasks is exported from @clerk/nextjs.

packages/vue/package.json (1)

3-3: LGTM — bump to 1.11.0 matches RedirectToTask → RedirectToTasks rename (verified)

  • packages/vue/package.json — "version": "1.11.0"
  • packages/vue/CHANGELOG.md — contains "## 1.11.0" and an entry mentioning "RedirectToTasks"
  • Repo search — no remaining occurrences of "RedirectToTask"

No changes required.

packages/shared/package.json (2)

3-3: Semver patch bump looks good.

Version moved to 3.20.1 with no other changes. Clear, minimal, and consistent with the PR scope.


3-3: CHANGELOG entry for 3.20.1 is present — no action required

Verified: packages/shared/package.json version = 3.20.1 and packages/shared/CHANGELOG.md contains header "## 3.20.1" (line 3).

packages/expo-passkeys/package.json (2)

3-3: Expo Passkeys version bump is correct.

Patch bump to 0.3.30 aligns with dependency updates; no API surface change here.


3-3: Confirmed — version and peer range OK

package.json version 0.3.30 matches CHANGELOG, and peerDependency "expo: >=50 <54" includes the devDependency "expo: ~52.0.47" — no changes required.

  • packages/expo-passkeys/package.json — "version": "0.3.30"; devDependencies.expo: "~52.0.47"; peerDependencies.expo: ">=50 <54"
  • packages/expo-passkeys/CHANGELOG.md — contains "## 0.3.30" (line 3)
packages/localizations/CHANGELOG.md (2)

3-9: Changelog entry reads well and matches the patch scope.

Entry 3.21.1 correctly notes the dependency bump to @clerk/[email protected]. Looks consistent with other packages in this release wave.


3-9: No action needed — package.json version matches CHANGELOG (3.21.1)

Verified:

  • packages/localizations/package.json — version: 3.21.1
  • packages/localizations/CHANGELOG.md — contains "## 3.21.1" (line 3)
packages/chrome-extension/CHANGELOG.md (1)

3-11: Confirmed: chrome-extension package.json version and @clerk/ deps align with CHANGELOG 2.5.20*

  • packages/chrome-extension/package.json — version = 2.5.20; @clerk/clerk-js: workspace:^, @clerk/clerk-react: workspace:^, @clerk/shared: workspace:^
  • packages/chrome-extension/CHANGELOG.md — contains "## 2.5.20" (line 3)

No changes required.

packages/express/package.json (3)

3-3: Express package patch bump is fine.

1.7.20 matches the dependency update wave; no API/export surface changes in this file.


3-3: CHANGELOG entry for 1.7.20 is present — no action needed

Verified:

  • packages/express/package.json — version is "1.7.20"
  • packages/express/CHANGELOG.md — contains "## 1.7.20" (line 3)

3-3: Spot-check (backend 2.9.0): m2mTokens.verifySecret only in tests — no runtime change required

Search results show m2mTokens.verifySecret only in test/integration files:

  • packages/backend/src/api/tests/M2MTokenApi.test.ts (lines ~303, ~329)
  • integration/tests/machine-auth/m2m.test.ts (line ~57)

No occurrences found in production code or migrations. No action required for runtime; tests may be updated later if desired.

packages/expo-passkeys/CHANGELOG.md (1)

3-10: Changelog entry is accurate and consistent with repo-wide bumps.

Patch section correctly lists dependency updates to @clerk/[email protected] and @clerk/[email protected] with commit refs. Semantic versioning is respected.

packages/agent-toolkit/CHANGELOG.md (2)

3-11: Changelog entry LGTM.

Patch entry correctly reflects dependency updates to @clerk/[email protected], @clerk/[email protected], and @clerk/[email protected] with SHAs. Versioning is consistent.


7-10: No deprecated m2m "secret" API usages found in code — only docs/CLI mention "secret".

I searched for usages of verifySecret, verifyToken, .secret (and the token "secret") inside packages/agent-toolkit. No code paths reference the deprecated m2m API; the occurrences are documentation/CLI flags only:

  • packages/agent-toolkit/README.md — references to "Clerk secret key", CLERK_SECRET_KEY env var, and examples using --secret-key / --secret-key=sk_123.
  • packages/agent-toolkit/src/modelcontextprotocol/local-server.ts — yargs option('secret-key') with description "Clerk secret key".

Action: no code changes required to address the @clerk/[email protected] rename. If you want to avoid user confusion, consider a follow-up doc/CLI wording change (optional) to mention "token" or clarify that the env/CLI flag is the project API key.

packages/chrome-extension/package.json (1)

3-4: Approve: version bump to 2.5.20 — changelog entry present

package.json updated to 2.5.20 and CHANGELOG contains the "## 2.5.20" entry (packages/chrome-extension/CHANGELOG.md:3).

  • packages/chrome-extension/package.json — "version": "2.5.20"
  • packages/chrome-extension/CHANGELOG.md — line 3: "## 2.5.20"
packages/localizations/package.json (1)

3-4: Localizations package version bump is correct.

Metadata-only change, complies with monorepo publishing rules and semver. Dependencies point to workspace @clerk/types as expected.

packages/astro/CHANGELOG.md (1)

3-11: Astro changelog patch entry aligns with dependency updates.

Accurately documents bumps to @clerk/[email protected], @clerk/[email protected], and @clerk/[email protected] with commit references. No functional notes needed for a pure dependency patch.

packages/remix/CHANGELOG.md (1)

3-6: Changelog entry looks good and follows conventions

Version header and section categorization (Minor/Patch) are clear and consistent with prior entries.

packages/fastify/CHANGELOG.md (1)

3-11: LGTM: Patch entry accurately reflects dependency bumps

The dependency versions match the coordinated release wave. No content issues spotted in this entry.

packages/elements/CHANGELOG.md (1)

3-11: Verified: package.json version matches CHANGELOG; workspace deps are expected

packages/elements/package.json version is 0.23.53 and packages/elements/CHANGELOG.md contains "## 0.23.53". The @clerk/* dependencies in package.json are declared as "workspace:^" (monorepo workspace refs) while the changelog lists the resolved package versions (e.g., @clerk/[email protected], @clerk/[email protected], @clerk/[email protected]). This is expected for a workspace-managed repo — no changes required.

Files checked:

  • packages/elements/package.json — version: 0.23.53; @clerk/* deps: "workspace:^"
  • packages/elements/CHANGELOG.md — top entry "## 0.23.53" with dependency notes
packages/themes/CHANGELOG.md (2)

3-9: Patch entry is clear and consistent

New 2.4.9 entry and dependency reference look good.


3-9: Sanity-check — themes version and @clerk/types alignment verified

Confirmed:

  • packages/themes/package.json — version: 2.4.9; dependency "@clerk/types": "workspace:^"
  • packages/types/package.json — @clerk/[email protected]
  • packages/themes/CHANGELOG.md contains "## 2.4.9"

Conclusion: the CHANGELOG version matches package.json and the workspace:^ dependency will resolve to @clerk/types 4.77.0 — no changes required.

packages/express/CHANGELOG.md (2)

3-11: Changelog entry aligns with dependency updates

Patch entry for 1.7.20 and dependency bumps read well.


3-11: Express 1.7.20 matches CHANGELOG; confirm workspace package versions

packages/express/package.json is version 1.7.20 and packages/express/CHANGELOG.md contains "## 1.7.20". However, @clerk/backend, @clerk/types and @clerk/shared are declared as "workspace:^" in packages/express/package.json (so this file doesn't show concrete versions). Confirm the actual workspace package versions match the changelog ( @clerk/backend → 2.9.0, @clerk/types → 4.77.0, @clerk/shared → 3.20.1) or update the dependency constraints to the intended pinned ranges.

Files to check:

  • packages/express/package.json
  • packages/express/CHANGELOG.md
  • package.json for the workspace packages that provide @clerk/backend, @clerk/types, @clerk/shared — verify their "version" fields match the changelog (or adjust constraints here).
packages/vue/CHANGELOG.md (1)

3-14: Rename verified — no remaining code references to RedirectToTask

Brief: I searched the repo — there are no exact matches for the old symbol RedirectToTask in code (only changelogs mention the rename). The new symbol RedirectToTasks is present and exported where expected.

Key locations:

  • No code occurrences of: RedirectToTask (none found)
  • Exports / occurrences of RedirectToTasks:
    • packages/vue/src/components/controlComponents.ts:63 — export const RedirectToTasks = defineComponent(...)
    • packages/react/src/components/controlComponents.tsx:169 — export const RedirectToTasks = withClerk(...)
    • packages/react/src/components/index.ts: (references RedirectToTasks)
    • packages/nextjs/src/client-boundary/controlComponents.ts (references RedirectToTasks)
    • Snapshot updates: packages/tanstack-react-start/src/tests/snapshots/exports.test.ts.snap, packages/remix/src/tests/snapshots/exports.test.ts.snap, packages/react-router/src/tests/snapshots/exports.test.ts.snap
    • Changelogs noting the rename: packages/vue/CHANGELOG.md, packages/react/CHANGELOG.md, packages/nextjs/CHANGELOG.md, packages/react-router/CHANGELOG.md, packages/tanstack-react-start/CHANGELOG.md, packages/remix/CHANGELOG.md

Action: No changes required from this review — the rename is applied across the codebase and exports reference the new name.

packages/shared/CHANGELOG.md (2)

3-11: Entry looks good and is consistent with repo-wide bumps.

Changelog correctly documents the patch, PR link, author attribution, and dependent package bumps to @clerk/[email protected].


9-11: No action needed — packages/shared already tracks @clerk/[email protected] via workspace protocol

packages/types/package.json shows "version": "4.77.0", and packages/shared/package.json declares "@clerk/types": "workspace:^", so it already resolves to the workspace package at 4.77.0.

Files to note:

  • packages/shared/package.json — dependencies["@clerk/types"] -> "workspace:^"
  • packages/types/package.json — "version" -> "4.77.0"
  • packages/shared/CHANGELOG.md — lists @clerk/[email protected] (matches workspace version)
packages/testing/CHANGELOG.md (2)

3-11: Changelog entry looks correct and consistent with upstream bumps.

Version 1.10.14 lists only dependency updates and matches the repo-wide versions.


3-11: Quick sanity check — testing version OK; workspace deps need explicit verification

packages/testing/package.json is @clerk/[email protected] (confirmed). Its @clerk/* deps are declared as workspace:^, so their concrete versions aren’t visible here — please confirm the actual workspace package versions match the CHANGELOG ( @clerk/backend 2.9.0, @clerk/types 4.77.0, @clerk/shared 3.20.1 ).

Files to check:

  • packages/testing/package.json — version OK
  • packages/backend/package.json — should be 2.9.0
  • packages/types/package.json — should be 4.77.0
  • packages/shared/package.json — should be 3.20.1

Suggested quick check:
for p in backend types shared; do jq -r '.name + "@" + .version' packages/$p/package.json; done

packages/react-router/CHANGELOG.md (2)

11-16: LGTM on dependency bumps.

The listed versions match the rest of the release train in this PR.


5-8: Rename verified — no remaining references to RedirectToTask; RedirectToTasks present

Searched the repo (excluding CHANGELOG.md, dist/build, node_modules): no matches for RedirectToTask. RedirectToTasks is present in the codebase at:

  • packages/vue/src/components/controlComponents.ts
  • packages/react/src/components/controlComponents.tsx
  • packages/react/src/components/index.ts
  • packages/nextjs/src/client-boundary/controlComponents.ts
  • packages/remix/src/tests/snapshots/exports.test.ts.snap
  • packages/tanstack-react-start/src/tests/snapshots/exports.test.ts.snap
  • packages/react-router/src/tests/snapshots/exports.test.ts.snap

No further action required.

packages/tanstack-react-start/CHANGELOG.md (2)

11-16: Dependencies section is consistent with the rest of the monorepo release.

No issues spotted.


5-8: No stale usages of RedirectToTask found — rename looks complete

I searched the repo (excluding build artifacts) and found no code references to the old symbol; only historical mentions remain in CHANGELOGs. Code and test snapshots use RedirectToTasks.

Files of note:

  • packages/tanstack-react-start/CHANGELOG.md — changelog entry (expected)
  • packages/react/src/components/controlComponents.tsx — defines RedirectToTasks
  • packages/react/src/components/index.ts — exports RedirectToTasks
  • packages/nextjs/src/client-boundary/controlComponents.ts — references RedirectToTasks
  • packages/vue/src/components/controlComponents.ts — defines RedirectToTasks
  • various snapshots (e.g. packages/*/src/tests/snapshots/exports.test.ts.snap) — updated to "RedirectToTasks"

No re-exports or aliases for the old name were found. No action required.

packages/clerk-js/CHANGELOG.md (1)

3-32: Clear, actionable entry with a practical example — nice work

The 5.84.0 section reads well, links are correct, and the example neatly shows the intended before-activation navigation flow. Dependency bumps are listed consistently with prior entries.

packages/nextjs/CHANGELOG.md (1)

7-7: Confirm whether this rename is breaking or aliased

I searched the repo for exports/aliases of RedirectToTask/RedirectToTasks; no occurrences or aliasing were found under packages/. The changelog entry currently reads:

Action requested (pick one):

  • If RedirectToTask was intentionally removed: update the changelog to mark this as a BREAKING CHANGE and call out required consumer updates.
  • If an alias/deprecation was added for backward compatibility: update the changelog to state that RedirectToTask remains as a deprecated alias (and mention removal timeline).

Files to check before updating:

  • packages/nextjs/CHANGELOG.md (line ~7)
  • package exports and built artifacts for nextjs (e.g., packages/nextjs/src, packages/nextjs/dist or types) to confirm whether an alias exists.

Comment on lines 3 to 49
## 2.9.0

### Minor Changes

- Remove `secret` in favor of `token` in m2m response. ([#6542](https://github.com/clerk/javascript/pull/6542)) by [@wobsoriano](https://github.com/wobsoriano)

Before:

```ts
const result = await clerkClient.m2mTokens.create();

console.log(result.secret);
```

After:

```ts
const result = await clerkClient.m2mTokens.create();

console.log(result.token);
```

- Deprecates `clerkClient.m2mTokens.verifySecret({ secret: 'mt_xxx' })` in favor or `clerkClient.m2mTokens.verifyToken({ token: 'mt_xxx' })` ([#6536](https://github.com/clerk/javascript/pull/6536)) by [@wobsoriano](https://github.com/wobsoriano)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify tests cover the rename and deprecation path

The public API changes are significant (response property rename and method deprecation). Please ensure there is test coverage for:

  • m2mTokens.create() returning token (and not secret)
  • m2mTokens.verifyToken() happy/edge paths
  • Backward-compat docs/samples not relying on verifySecret

I can help generate a migration check, but first please run the script below to assess repo usage and tests.


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Search repo for old API usages that should be updated:"
rg -n --hidden --glob '!*dist*' --glob '!*build*' $'m2mTokens\\.verifySecret\\(' || true
rg -n --hidden --glob '!*dist*' --glob '!*build*' $'result\\.secret\\b' || true

echo
echo "Search for new API usages and test coverage:"
rg -n --hidden --glob '!*dist*' --glob '!*build*' $'m2mTokens\\.verifyToken\\(' -A 3 || true
rg -n --hidden --glob '!*dist*' --glob '!*build*' $'m2mTokens\\.create\\(' -A 5 | rg -n $'token\\b' -A 0 || true

echo
echo "List likely test files that mention m2m tokens:"
fd -t f -e ts -e tsx -e js -e mjs -e cts -e mts | rg -n $'m2mTokens|verifyToken|verifySecret|mt_' || true

Length of output: 5207


Verify tests cover the rename and deprecation path — leftover verifySecret usages need attention

Quick check: the repo already has tests for the new API (create() -> .token, verifyToken) but there are remaining verifySecret usages that should be either removed/updated or explicitly tested as the deprecation/fallback path.

Files to fix or confirm (from the search results)

  • packages/backend/src/api/tests/M2MTokenApi.test.ts — calls to apiClient.m2mTokens.verifySecret(...) (lines ~303, ~329)
  • integration/tests/machine-auth/m2m.test.ts — clerkClient.m2mTokens.verifySecret({ secret }) (line ~57)
  • packages/backend/CHANGELOG.md — examples referencing result.secret and verifySecret (lines ~14, ~25, ~108, ~116)

Notes:

  • New API coverage exists in tests (e.g., M2MTokenApi.test.ts around lines ~226–255, factory.test.ts, and src/tokens/verify.ts).
  • Action: either update the remaining verifySecret usages to verifyToken, or keep them only as explicit deprecation/back-compat tests that assert expected fallback behavior (and document the deprecation). Also ensure m2mTokens.create() tests expect .token (not .secret).

I can help open a small PR to replace usages or add deprecation tests if you want.

@@ -1,6 +1,6 @@
{
"name": "@clerk/backend",
"version": "2.8.0",
"version": "2.9.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Version bump to 2.9.0 — semver and metadata look correct (LGTM).

Matches the changelog (m2m secret→token rename, deprecations) and workspace deps. No packaging/export changes here.

Run this to double-check repo-wide migration consistency (no lingering verifySecret/result.secret usages) and the changelog entry:

Also consider adding/adjusting unit/integration tests that cover verifyToken({ token }) and the new m2m response shape in @clerk/backend to prevent regressions.


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Check backend changelog has 2.9.0 entry"
rg -n $'^##\\s*2\\.9\\.0' packages/backend/CHANGELOG.md || { echo "Missing 2.9.0 entry in backend changelog"; exit 1; }

echo "Search for deprecated m2mTokens.verifySecret(...) usages"
rg -n --hidden --glob '!*dist/*' --glob '!*CHANGELOG.md' $'m2mTokens\\.verifySecret\\s*\\(' || echo "No deprecated usages found"

echo "Search for result.secret linked to m2mTokens.create(...)"
# Look for .secret within a small window around m2mTokens.create calls
rg -n --hidden --glob '!*dist/*' --glob '!*CHANGELOG.md' $'m2mTokens\\.create' -A4 -B2 | rg -n $'\\.secret' || echo "No '.secret' usages near m2mTokens.create calls"

Length of output: 1286


Action required — tests using deprecated m2m API need updating; changelog OK

Changelog check passed (packages/backend/CHANGELOG.md contains "## 2.9.0"), but there are remaining deprecated usages in tests and a few .secret references that should be reviewed.

Files to fix:

  • packages/backend/src/api/tests/M2MTokenApi.test.ts — m2mTokens.verifySecret at lines ~303 and ~329
  • integration/tests/machine-auth/m2m.test.ts — m2mTokens.verifySecret at ~line 57
  • integration/tests/machine-auth/m2m.test.ts — .secret references at ~lines 85, 95, 168 (these reference server.secretKey values)

Requested changes:

  • Replace deprecated m2mTokens.verifySecret(...) calls in tests with the new verifyToken({ token }) usage.
  • Ensure tests/assertions are updated to match the new m2m response shape (replace any result.secret expectations with the new token field as appropriate).
  • Add or adjust unit/integration tests in @clerk/backend to cover verifyToken({ token }) and the new m2m response shape to prevent regressions.
🤖 Prompt for AI Agents
In packages/backend/package.json around line 3, tests still use the deprecated
m2m API; update the three test files listed: replace m2mTokens.verifySecret(...)
calls in packages/backend/src/api/__tests__/M2MTokenApi.test.ts (around lines
~303 and ~329) and integration/tests/machine-auth/m2m.test.ts (around line ~57)
with the new verifyToken({ token }) call, adjust assertions to expect the new
response shape (replace any result.secret expectations with the new token field
or other renamed properties), and replace or remove direct .secret accesses in
integration/tests/machine-auth/m2m.test.ts at ~lines 85, 95, 168 to reference
server.secretKey usage compatible with the new API; add/adjust unit and
integration tests in @clerk/backend to cover verifyToken({ token }) and the new
m2m response shape to prevent regressions.

Comment on lines 3 to 12
## 1.8.6

### Patch Changes

- Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27)]:
- @clerk/[email protected]
- @clerk/[email protected]
- @clerk/[email protected]
- @clerk/[email protected]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Changelog entry looks good; consider deduping commit refs and verify version sync

The 1.8.6 entry correctly documents patch-level dependency updates. Minor nit: the commit reference 69498df appears twice in the bracket list; consider deduplicating for clarity.

Also, since this is a release-only change with dependency bumps, ensure CI/e2e matrix passes against Nuxt 3.17.x and the updated @clerk/* packages.

Run this to verify package.json version matches the latest changelog entry:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

PKG="packages/nuxt/package.json"
CHANGELOG="packages/nuxt/CHANGELOG.md"

pkg_ver="$(jq -r .version "$PKG")"
ch_ver="$(grep -m1 -E '^## [0-9]+\.[0-9]+\.[0-9]+' "$CHANGELOG" | awk '{print $2}')"

echo "package.json version:   $pkg_ver"
echo "CHANGELOG latest entry: $ch_ver"

if [[ "$pkg_ver" == "$ch_ver" ]]; then
  echo "OK: Versions are in sync."
else
  echo "ERROR: Versions are not in sync." >&2
  exit 1
fi

Length of output: 485


Changelog OK — versions in sync (1.8.6); please dedupe duplicate commit ref

Verified: packages/nuxt/package.json and packages/nuxt/CHANGELOG.md both report v1.8.6.

  • Fix: packages/nuxt/CHANGELOG.md — the commit ref 69498df appears twice in the dependency commit list; remove the duplicate for clarity.
  • Please also ensure CI/e2e matrix passes against Nuxt 3.17.x with the bumped @clerk/* packages.

Suggested corrected snippet:

## 1.8.6

### Patch Changes

- Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
  - @clerk/[email protected]
  - @clerk/[email protected]
  - @clerk/[email protected]
  - @clerk/[email protected]
🤖 Prompt for AI Agents
packages/nuxt/CHANGELOG.md lines 3-12: the commit reference `69498df` is
duplicated in the "Updated dependencies" list; remove the duplicate occurrence
so each commit hash appears only once (update the inline bracketed list to
contain d400782, 69498df, 2db7431, 59f1559) and keep the dependency bullets
unchanged, then run the CI/e2e matrix ensuring tests pass against Nuxt 3.17.x
with the bumped @clerk/* packages.

@@ -1,6 +1,6 @@
{
"name": "@clerk/react-router",
"version": "1.8.13",
"version": "1.9.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Confirm deprecation alias and changelog entry exist.
This helps avoid an accidental breaking change for consumers.


🏁 Script executed:

#!/bin/bash
set -euo pipefail

pkg="packages/react-router"
ver=$(jq -r .version "$pkg/package.json")

echo "Checking changelog for $ver..."
rg -n "## $ver" "$pkg/CHANGELOG.md" || { echo "Missing changelog entry for $ver"; exit 1; }

echo "Looking for 'RedirectToTask' references (alias/deprecation)..."
rg -n -S "RedirectToTask" "$pkg" -g '!dist' -A 2 || {
  echo "No references found. If there's no alias, confirm this is a deliberate breaking change and consider a major bump or an alias.";
}

Length of output: 1044


🏁 Script executed:

#!/bin/bash
set -euo pipefail

pkg="packages/react-router"

echo "Searching for RedirectToTasks occurrences..."
rg -n -S "RedirectToTasks" "$pkg" -g '!dist' -A 2 || true

echo
echo "Searching for RedirectToTask (old name) occurrences..."
rg -n -S "RedirectToTask" "$pkg" -g '!dist' -A 2 || true

echo
echo "Looking for export lines that mention Redirect (to find barrel/index exports)..."
rg -n -S "export .*Redirect" "$pkg" -g '!dist' -A 2 || true

Length of output: 2646


🏁 Script executed:

#!/bin/bash
set -euo pipefail

pkg="packages/react-router"

echo "package.json relevant fields:"
jq '{name,version,main,module,types,exports}' "$pkg/package.json" || true

echo
echo "=== tests/exports.test.ts ==="
sed -n '1,240p' "$pkg/src/__tests__/exports.test.ts" || true

echo
echo "=== tests snapshot (exports.test.ts.snap) ==="
sed -n '1,240p' "$pkg/src/__tests__/__snapshots__/exports.test.ts.snap" || true

echo
echo "Searching for export statements in src (public API barrels / exports):"
rg -n -S "export .*from|export \\{.*\\}|export default" "$pkg/src" -g '!dist' -A 2 || true

echo
echo "Top-level src files and directories:"
ls -la "$pkg/src" || true

Length of output: 5351


Action required: add a deprecation alias for RedirectToTask or confirm deliberate breaking change

Changelog contains a 1.9.0 entry renaming RedirectToTask → RedirectToTasks, but I found no alias/export for the old name in the codebase — only the changelog mentions the old name. You should either provide a compatibility alias or treat this as a breaking change and bump/announce accordingly.

Files/locations inspected (evidence)

  • packages/react-router/package.json — version 1.9.0
  • packages/react-router/CHANGELOG.md — “Rename RedirectToTask … to RedirectToTasks” (line ~7)
  • packages/react-router/src/tests/snapshots/exports.test.ts.snap — public exports snapshot shows "RedirectToTasks"
  • packages/react-router/src/client/ReactRouterClerkProvider.tsx — re-exports from '@clerk/clerk-react'
  • packages/react-router/src/index.ts and packages/react-router/src/client/index.ts — public re-export barrels

Recommended fixes

  • Add a backward-compatible alias export (so consumers using the old name won’t break). For example, add to packages/react-router/src/client/index.ts (or another barrel file that re-exports the external components):

export { RedirectToTasks as RedirectToTask } from '@clerk/clerk-react';

  • Update the snapshot/tests to account for the alias (or intentionally avoid adding the alias and document the breaking change + bump version accordingly).
  • Update the changelog to explicitly state whether the old name is deprecated with an alias or intentionally removed.
🤖 Prompt for AI Agents
In packages/react-router/package.json around line 3, the changelog shows
RedirectToTask was renamed to RedirectToTasks but no compatibility export
exists; either add a backward-compatible alias export or treat it as a breaking
change. To add the alias: in packages/react-router/src/client/index.ts (or
packages/react-router/src/index.ts) add the line `export { RedirectToTasks as
RedirectToTask } from '@clerk/clerk-react';`, then update the public-exports
snapshot/tests to include the alias; alternatively, if you intend this to be a
breaking change, revert adding the alias, increment the package major version in
package.json and update CHANGELOG.md to explicitly state the removal.

Comment on lines +5 to +8
### Minor Changes

- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Clarify migration for the renamed component and verify back-compat alias

Renaming an exported component can be breaking if no alias remains. Please add a short migration note here and confirm whether RedirectToTask is still re-exported (deprecated) for a grace period. If no alias exists, consider explicitly calling out the breaking nature of this change.

Run this script to verify whether an alias/back-compat export still exists anywhere in the repo and to surface usages that might need migration:

Apply this change to include a concise migration snippet under Minor Changes:

 ### Minor Changes

-- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+  - Migration:
+    ```diff
+    - import { RedirectToTask } from '@clerk/clerk-react'
+    + import { RedirectToTasks } from '@clerk/clerk-react'
+    ```
+    If you rely on the old name, update imports accordingly. If a deprecation alias exists, consider migrating proactively to avoid future breakages.

I can also generate a codemod (jscodeshift/ts-morph) to automatically update imports across packages—want me to include it?


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Searching for exports of RedirectToTask and RedirectToTasks…"
rg -n -S --glob '!*dist*' --glob '!*node_modules*' $'export .*RedirectToTask|export .*RedirectToTasks' -A 2 -B 2 || true

echo
echo "Searching for usages of RedirectToTask across the repo (may indicate migration needs)…"
rg -n -S --glob '!*dist*' --glob '!*node_modules*' $'RedirectToTask' -A 2 -B 2 || true

Length of output: 8013


Action required: Add migration note or restore back-compat alias — no RedirectToTask re-export found

Verification summary: a repo search shows only RedirectToTasks exports (e.g. packages/react/src/components/index.ts, packages/react/src/components/controlComponents.tsx, packages/vue/src/components/controlComponents.ts, packages/nextjs/src/client-boundary/controlComponents.ts). RedirectToTask only appears in CHANGELOGs/snapshots — there is no back-compat RedirectToTask export/alias. This rename is therefore breaking unless you add a deprecated alias or call out the breaking change in the changelogs.

Files to update (suggested)

  • Add migration note to changelogs that list the rename:
    • packages/react/CHANGELOG.md
    • packages/vue/CHANGELOG.md
    • packages/remix/CHANGELOG.md
    • packages/nextjs/CHANGELOG.md
    • packages/tanstack-react-start/CHANGELOG.md
    • packages/react-router/CHANGELOG.md
  • If you want back-compat, add a deprecated alias in the public exports (examples below):
    • packages/react/src/components/index.ts
    • (and any other package index that re-exports the control components, e.g. nextjs client-boundary)

Suggested CHANGELOG update (concise migration snippet)

 ### Minor Changes

 - Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+  - Migration:
+    ```diff
+    - import { RedirectToTask } from '@clerk/clerk-react'
+    + import { RedirectToTasks } from '@clerk/clerk-react'
+    ```
+    Note: repository search shows no `RedirectToTask` re-export/alias — this is a breaking rename. Either add a deprecated alias in the exports (example below) or explicitly mark this as breaking so consumers can migrate.

Suggested (optional) back-compat export to add

# packages/react/src/components/index.ts
+ // Deprecated alias for back-compat — remove in next major
+ export { RedirectToTasks as RedirectToTask }

I can also generate a jscodeshift/ts-morph codemod to update imports across the repo if you want—should I include it?

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Minor Changes
- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
### Minor Changes
- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
- Migration:
🤖 Prompt for AI Agents
In packages/react/CHANGELOG.md around lines 5-8: the changelog renames
RedirectToTask to RedirectToTasks but provides no migration note or back-compat
alias, which is a breaking change; either add a concise migration note to the
listed changelogs (packages/react, vue, remix, nextjs, tanstack-react-start,
react-router) showing the old -> new import and telling users to rename, or
restore backward compatibility by adding a deprecated alias export named
RedirectToTask that re-exports RedirectToTasks in each public index (e.g.
packages/react/src/components/index.ts and other package index
files/client-boundary files), and update tests/snapshots if needed; choose one
approach and apply consistently across all affected packages.

@@ -1,6 +1,6 @@
{
"name": "@clerk/clerk-react",
"version": "5.41.1",
"version": "5.42.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Ensure migration safety for the component rename and consider test coverage.

  • Verify an export alias for RedirectToTask exists (deprecated) to avoid breaking apps pinned to minor versions.
  • Since this affects a public component, consider adding/adjusting tests or smoke tests to cover both the new RedirectToTasks and the deprecated alias (if present).

🏁 Script executed:

#!/bin/bash
set -euo pipefail

pkg="packages/react"
ver=$(jq -r .version "$pkg/package.json")

echo "Checking changelog for $ver..."
rg -n "## $ver" "$pkg/CHANGELOG.md" || { echo "Missing changelog entry for $ver"; exit 1; }

echo "Scanning for 'RedirectToTask' (alias) and 'RedirectToTasks' (new export)..."
rg -n -S "RedirectTo(Task|Tasks)" "$pkg" -g '!dist' -A 2 || echo "No component references found in sources."

echo "Checking tests mention either name (if tests exist in this package)..."
rg -n -S "RedirectTo(Task|Tasks)" "$pkg" -g '!dist' -A 2 || echo "No tests referencing the components found."

Length of output: 3168


Add a deprecated alias for RedirectToTask and add tests to ensure a safe rename

Changelog shows the component was renamed to RedirectToTasks, but the source only exports RedirectToTasks (no RedirectToTask alias) and there are no tests referencing either export — this can break consumers pinned to minor versions. Please add a backward-compatible alias and tests.

Files to change

  • packages/react/src/components/controlComponents.tsx — add deprecated alias export
  • packages/react/src/components/index.ts — export the alias from the public API
  • add tests (e.g. packages/react/src/components/tests/redirectToTasks.test.tsx) that cover both RedirectToTasks and the deprecated RedirectToTask alias

Suggested diffs

packages/react/src/components/controlComponents.tsx

 export const RedirectToTasks = withClerk(({ clerk }: WithClerkProp) => {
   React.useEffect(() => {
     void clerk.redirectToTasks();
   }, 'RedirectToTasks');
 });
 
+/** @deprecated Use RedirectToTasks instead. Kept for backward compatibility. */
+export const RedirectToTask = RedirectToTasks;

packages/react/src/components/index.ts

   RedirectToTasks,
+  RedirectToTask,

Test guidance (very short)

  • Add a unit / smoke test that imports both RedirectToTasks and RedirectToTask and asserts they mount and trigger clerk.redirectToTasks (mock the clerk). This ensures the alias remains a drop-in replacement until removed in a major release.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In packages/react/src/components/controlComponents.tsx around the
RedirectToTasks component definition, add a deprecated alias export named
RedirectToTask that simply re-exports or points to RedirectToTasks (mark with a
JSDoc @deprecated), then in packages/react/src/components/index.ts export
RedirectToTask from ./controlComponents so the alias is part of the public API;
finally add a new test file
packages/react/src/components/__tests__/redirectToTasks.test.tsx that mocks the
clerk object, imports both RedirectToTasks and RedirectToTask, mounts/renders
them (shallow or render) and asserts that invoking the component behavior
triggers clerk.redirectToTasks for both imports to ensure backward compatibility
until the next major release.

@@ -1,6 +1,6 @@
{
"name": "@clerk/remix",
"version": "4.10.13",
"version": "4.11.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify non-breaking rename (ensure deprecated alias is still exported).
If RedirectToTask was removed without an alias, this would be breaking. Please confirm an alias/export remains and that the changelog documents the migration.

Run this script to validate the changelog entry exists and to scan for the legacy export:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

pkg="packages/remix"

echo "Checking changelog entry matches package.json version..."
ver=$(jq -r .version "$pkg/package.json")
rg -n "## $ver" "$pkg/CHANGELOG.md" || { echo "Missing changelog entry for $ver"; exit 1; }

echo "Scanning for deprecated alias 'RedirectToTask' to prevent breaking change..."
rg -n -S "RedirectToTask" "$pkg" -g '!dist' -A 2 || {
  echo "No references found. If intentional, confirm this was communicated as a breaking change or provide a compatibility alias.";
}

Length of output: 1055


Action required — add compatibility alias for RedirectToTask or mark as breaking

Changelog documents the rename to RedirectToTasks (packages/remix/CHANGELOG.md) but a scan of packages/remix shows no occurrences of the legacy name RedirectToTask and the tests snapshot only contains "RedirectToTasks" (packages/remix/src/tests/snapshots/exports.test.ts.snap). That indicates no deprecated alias/export remains — this is a breaking change for consumers.

Please either:

  • Add a compatibility export in the package's public exports (example: export { RedirectToTasks as RedirectToTask }), or
  • Explicitly mark this as a breaking change in the changelog/release notes and add migration guidance.

Files to review:

  • packages/remix/CHANGELOG.md
  • packages/remix/src/tests/snapshots/exports.test.ts.snap
  • the remix package's public entry (root exports) — add the alias there
🤖 Prompt for AI Agents
In packages/remix/package.json around line 3, the version bump removes the
legacy RedirectToTask export causing a breaking change; to fix, add a
compatibility alias in the remix package's public entry (root exports file,
e.g., packages/remix/src/index.ts or whichever file is listed as the package's
main/exports) by exporting the new name under the old name (export {
RedirectToTasks as RedirectToTask }) so consumers still import the legacy
identifier, and update the package's CHANGELOG.md to either note this as a
breaking change with migration guidance or remove the alias and clearly mark the
change as breaking per the review; ensure tests and snapshots reflect the alias
if you add it.

@@ -1,6 +1,6 @@
{
"name": "@clerk/types",
"version": "4.76.0",
"version": "4.77.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Quick repo-wide sanity check for renamed/removed APIs.

Given the deprecations/renames mentioned in the PR (verifySecret → verifyToken, secret → token, RedirectToTask → RedirectToTasks), run this to catch any lingering usages outside changelogs/changesets.


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Exclude changeset and changelog files
EXCLUDES=(-g '!.changeset/*' -g '!**/CHANGELOG.md' -g '!**/CHANGELOG.mdx')

echo "Searching for deprecated usages (should return no matches):"

echo "- m2mTokens.verifySecret({ secret })"
rg -n $'m2mTokens\\.verifySecret\\s*\\(' "${EXCLUDES[@]}"

echo "- result.secret from m2mTokens.create()"
rg -n $'result\\.secret\\b' "${EXCLUDES[@]}"

echo "- RedirectToTask (old name)"
rg -n $'\\bRedirectToTask\\b' "${EXCLUDES[@]}"

echo "Done."

Length of output: 966


Action required: update remaining deprecated m2mTokens.verifySecret usages (verifySecret → verifyToken; secret → token).

Quick check found 3 remaining occurrences that need fixing — replace the old API/name and update parameter/property names as appropriate:

  • packages/backend/src/api/tests/M2MTokenApi.test.ts — lines 303, 329
    • Replace: apiClient.m2mTokens.verifySecret(...) → apiClient.m2mTokens.verifyToken(...)
  • integration/tests/machine-auth/m2m.test.ts — line 57
    • Replace: clerkClient.m2mTokens.verifySecret({ secret }) → clerkClient.m2mTokens.verifyToken({ token: /* renamed variable or value */ })

Notes: no matches were found for result.secret or RedirectToTask (outside changesets/changelogs). After making changes, rerun the repo-wide search to confirm no remaining usages.

🤖 Prompt for AI Agents
packages/types/package.json (line 3) and update usages in
packages/backend/src/api/__tests__/M2MTokenApi.test.ts (lines ~303, ~329) and
integration/tests/machine-auth/m2m.test.ts (line 57): replace
apiClient.m2mTokens.verifySecret(...) with apiClient.m2mTokens.verifyToken(...),
and change any call shapes from { secret } to { token: /* appropriate value or
renamed variable */ } (rename local variables if needed), then run a repo-wide
search to ensure no remaining verifySecret or secret parameters remain.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (5)
packages/clerk-js/CHANGELOG.md (2)

5-24: Changelog entry is clear; consider adding the explicit type signature and behavior notes for navigate.

Nice addition and example. Two small improvements to reduce ambiguity for readers:

  • Show the TS signature of the navigate callback (payload shape and return type).
  • Clarify whether navigate is awaited and what happens if it throws (does it abort setActive?).

Proposed wording right after the bullet item:

 - Add `navigate` parameter to `clerk.setActive()` for custom navigation before the session and/or organization is set. ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+
+  Type:
+  - `navigate?: (payload: { session: Session }) => Promise<void>`
+
+  Notes:
+  - `navigate` is awaited before `setActive` completes.
+  - If the callback throws, `setActive` will be aborted and the error will be propagated to the caller.

7-7: Standardize the API name casing for consistency.

Elsewhere in the changelog, API references often use Clerk.setActive(). Consider aligning this entry to use the same casing unless the lowercase clerk is intentionally referring to an instance.

- - Add `navigate` parameter to `clerk.setActive()` for custom navigation before the session and/or organization is set. ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+ - Add `navigate` parameter to `Clerk.setActive()` for custom navigation before the session and/or organization is set. ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)

If the lowercase clerk is intentional (referring to a runtime instance), feel free to keep it—just ensure surrounding entries follow the same convention.

packages/nextjs/CHANGELOG.md (3)

5-8: Clarify rename impact and add a brief migration example

The rename is clear, but a short migration snippet will help consumers scanning the changelog quickly adopt the change. Consider explicitly calling out import/component rename.

Apply this diff to enrich the entry:

 ### Minor Changes

-- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+- Rename `RedirectToTask` component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+  - Migration:
+    ```ts
+    // Before
+    import { RedirectToTask } from '@clerk/nextjs';
+    // After
+    import { RedirectToTasks } from '@clerk/nextjs';
+    ```
+  - Note: If `RedirectToTask` remains as a temporary alias, mark it as deprecated in docs and specify the removal target (next major).

7-7: Minor wording consistency

“control component” is inconsistent with prior entries (e.g., earlier sections just say “component”). Prefer “component” for consistency.

-- Rename `RedirectToTask` control component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)
+- Rename `RedirectToTask` component to `RedirectToTasks` ([#6486](https://github.com/clerk/javascript/pull/6486)) by [@LauraBeatris](https://github.com/LauraBeatris)

3-8: Add a small export smoke test for the renamed component

No tests are updated in this release PR (expected), but a quick export smoke test reduces the risk of accidental regressions when renaming exports.

Example (place under @clerk/nextjs tests):

// packages/nextjs/__tests__/exports.spec.ts
import { RedirectToTasks } from '@clerk/nextjs';

describe('exports', () => {
  it('exposes RedirectToTasks', () => {
    expect(typeof RedirectToTasks).toBe('function');
  });
  // If you maintain a deprecation alias for one cycle, also test it:
  // import { RedirectToTask } from '@clerk/nextjs';
  // it('temporarily exposes deprecated RedirectToTask', () => {
  //   expect(typeof RedirectToTask).toBe('function');
  // });
});

I can open a follow-up PR adding this test if helpful.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8fdc6fb and 0357f13.

📒 Files selected for processing (49)
  • .changeset/chatty-kings-raise.md (0 hunks)
  • .changeset/rich-donuts-agree.md (0 hunks)
  • .changeset/small-adults-crash.md (0 hunks)
  • .changeset/upset-sides-kneel.md (0 hunks)
  • .changeset/warm-rocks-flow.md (0 hunks)
  • packages/agent-toolkit/CHANGELOG.md (1 hunks)
  • packages/agent-toolkit/package.json (1 hunks)
  • packages/astro/CHANGELOG.md (1 hunks)
  • packages/astro/package.json (1 hunks)
  • packages/backend/CHANGELOG.md (1 hunks)
  • packages/backend/package.json (1 hunks)
  • packages/chrome-extension/CHANGELOG.md (1 hunks)
  • packages/chrome-extension/package.json (1 hunks)
  • packages/clerk-js/CHANGELOG.md (1 hunks)
  • packages/clerk-js/package.json (1 hunks)
  • packages/elements/CHANGELOG.md (1 hunks)
  • packages/elements/package.json (1 hunks)
  • packages/expo-passkeys/CHANGELOG.md (1 hunks)
  • packages/expo-passkeys/package.json (1 hunks)
  • packages/expo/CHANGELOG.md (1 hunks)
  • packages/expo/package.json (1 hunks)
  • packages/express/CHANGELOG.md (1 hunks)
  • packages/express/package.json (1 hunks)
  • packages/fastify/CHANGELOG.md (1 hunks)
  • packages/fastify/package.json (1 hunks)
  • packages/localizations/CHANGELOG.md (1 hunks)
  • packages/localizations/package.json (1 hunks)
  • packages/nextjs/CHANGELOG.md (1 hunks)
  • packages/nextjs/package.json (1 hunks)
  • packages/nuxt/CHANGELOG.md (1 hunks)
  • packages/nuxt/package.json (1 hunks)
  • packages/react-router/CHANGELOG.md (1 hunks)
  • packages/react-router/package.json (1 hunks)
  • packages/react/CHANGELOG.md (1 hunks)
  • packages/react/package.json (1 hunks)
  • packages/remix/CHANGELOG.md (1 hunks)
  • packages/remix/package.json (1 hunks)
  • packages/shared/CHANGELOG.md (1 hunks)
  • packages/shared/package.json (1 hunks)
  • packages/tanstack-react-start/CHANGELOG.md (1 hunks)
  • packages/tanstack-react-start/package.json (1 hunks)
  • packages/testing/CHANGELOG.md (1 hunks)
  • packages/testing/package.json (1 hunks)
  • packages/themes/CHANGELOG.md (1 hunks)
  • packages/themes/package.json (1 hunks)
  • packages/types/CHANGELOG.md (1 hunks)
  • packages/types/package.json (1 hunks)
  • packages/vue/CHANGELOG.md (1 hunks)
  • packages/vue/package.json (1 hunks)
💤 Files with no reviewable changes (5)
  • .changeset/chatty-kings-raise.md
  • .changeset/warm-rocks-flow.md
  • .changeset/upset-sides-kneel.md
  • .changeset/small-adults-crash.md
  • .changeset/rich-donuts-agree.md
✅ Files skipped from review due to trivial changes (5)
  • packages/backend/package.json
  • packages/react-router/package.json
  • packages/localizations/CHANGELOG.md
  • packages/vue/package.json
  • packages/astro/CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (37)
  • packages/expo/package.json
  • packages/agent-toolkit/package.json
  • packages/nextjs/package.json
  • packages/chrome-extension/package.json
  • packages/nuxt/package.json
  • packages/tanstack-react-start/package.json
  • packages/themes/package.json
  • packages/expo-passkeys/package.json
  • packages/localizations/package.json
  • packages/remix/package.json
  • packages/react/package.json
  • packages/fastify/package.json
  • packages/elements/package.json
  • packages/types/package.json
  • packages/testing/package.json
  • packages/clerk-js/package.json
  • packages/react/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/astro/package.json
  • packages/chrome-extension/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/shared/package.json
  • packages/express/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/express/package.json
  • packages/testing/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/backend/CHANGELOG.md
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/clerk-js/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
packages/**/CHANGELOG.md

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Maintain detailed changelogs

Files:

  • packages/clerk-js/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
**/*

⚙️ CodeRabbit Configuration File

If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.

Files:

  • packages/clerk-js/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md

Comment on lines 26 to 33
### Patch Changes

- Updated dependencies [[`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
- @clerk/[email protected]
- @clerk/[email protected]
- @clerk/[email protected]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify dependency versions sync with package manifests.

The dependency versions listed here should match packages/clerk-js/package.json. Please verify to prevent release inconsistencies.

Run:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Find the clerk-js package.json
PKG_JSON="$(fd -a '^package\.json$' packages/clerk-js | head -n1)"
echo "Checking ${PKG_JSON}"

echo "Declared deps in package.json:"
jq -r '.dependencies | to_entries[] | select(.key|test("^@clerk/(types|shared|localizations)$")) | "\(.key): \(.value)"' "$PKG_JSON"

echo
echo "Changelog deps:"
cat <<'EOF'
@clerk/[email protected]
@clerk/[email protected]
@clerk/[email protected]
EOF

Length of output: 719


Changelog versions vs package.json mismatch — please align

CHANGELOG.md lists explicit versions for @clerk/types (4.77.0), @clerk/shared (3.20.1), and @clerk/localizations (3.21.1), but packages/clerk-js/package.json declares those deps as workspace:^ — update one or the other to avoid release inconsistencies.

Files to check:

  • packages/clerk-js/CHANGELOG.md — lines ~26–31 (current changelog block).
  • packages/clerk-js/package.json — dependencies: @clerk/types, @clerk/shared, @clerk/localizations (all set to workspace:^).

Changelog snippet:

### Patch Changes

- Updated dependencies [[`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
  - @clerk/[email protected]
  - @clerk/[email protected]
  - @clerk/[email protected]

package.json declared deps (verified):

@clerk/localizations: workspace:^
@clerk/shared: workspace:^
@clerk/types: workspace:^

Comment on lines 11 to 16
- Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`307dc3f`](https://github.com/clerk/javascript/commit/307dc3f05ba1bd3b30b491b198d9e65eebcc95f9), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27)]:
- @clerk/[email protected]
- @clerk/[email protected]
- @clerk/[email protected]
- @clerk/[email protected]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify dependency versions and deduplicate repeated commit hash

  • The dependency versions listed look right per PR objectives. Please verify they match the actual package.json for @clerk/nextjs.
  • The commit hash 69498df appears twice; consider removing duplicates to reduce noise.

Run this script to verify versions match package.json:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Find the nextjs package.json
NEXTJS_PKG=$(fd -a -t f package.json | gawk '/packages\/nextjs\/package\.json$/ {print; exit}')
if [[ -z "${NEXTJS_PKG:-}" ]]; then
  echo "Could not locate packages/nextjs/package.json"
  exit 1
fi

echo "Using ${NEXTJS_PKG}"

# Expected versions from changelog
exp_backend="2.9.0"
exp_types="4.77.0"
exp_shared="3.20.1"
exp_react="5.42.0"

echo "Reading declared deps..."
jq -r '.dependencies, .peerDependencies, .devDependencies' "$NEXTJS_PKG" > /tmp/deps.json

check_dep() {
  local name="$1" exp="$2"
  # Search all dep sections for the package (supports ^/~ ranges or exact)
  local found
  found=$(jq -r --arg n "$name" '
    to_entries | map(select(.value | has($n))) | .[]
    | "\(.key): \(.value[$n])"
  ' /tmp/deps.json)
  if [[ -z "$found" ]]; then
    echo "WARN: $name not found in dependencies/peer/dev deps"
    return
  fi
  echo "Found -> $found"
  # Strip leading range specifiers for comparison
  local ver
  ver=$(sed -E 's/^[\^~]//' <<< "$(awk -F': ' '{print $2}' <<< "$found")")
  if [[ "$ver" != "$exp" ]]; then
    echo "MISMATCH: $name expected $exp but found $ver"
    exit 2
  fi
}

check_dep "@clerk/backend" "$exp_backend"
check_dep "@clerk/types" "$exp_types"
check_dep "@clerk/shared" "$exp_shared"
check_dep "@clerk/clerk-react" "$exp_react"

echo "All listed dependency versions align with package.json."

Length of output: 1055


🏁 Script executed:

#!/bin/bash
set -euo pipefail

PKG="packages/nextjs/package.json"
CL="packages/nextjs/CHANGELOG.md"

if [[ ! -f "$PKG" ]]; then
  echo "ERROR: ${PKG} not found"
  exit 1
fi

echo "Using $PKG"
echo

# Combine deps into single object
jq '(.dependencies // {}) + (.peerDependencies // {}) + (.devDependencies // {})' "$PKG" > /tmp/combined_deps.json

for pkg in "@clerk/backend" "@clerk/types" "@clerk/shared" "@clerk/clerk-react"; do
  ver=$(jq -r --arg p "$pkg" 'if has($p) then .[$p] else empty end' /tmp/combined_deps.json || true)
  if [[ -z "$ver" ]]; then
    echo "$pkg: NOT FOUND"
  else
    norm=$(sed -E 's/^[\^~]//' <<< "$ver")
    echo "$pkg: declared \"$ver\" -> normalized \"$norm\""
  fi
done

echo
if [[ -f "$CL" ]]; then
  echo "Occurrences of commit hash 69498df in $CL:"
  grep -n '69498df' "$CL" || echo "none"
  echo
  echo "CHANGELOG snippet (lines 1-40):"
  sed -n '1,40p' "$CL"
else
  echo "CHANGELOG not found at $CL"
fi

Length of output: 5878


Remove duplicate commit hash in CHANGELOG & verify listed versions

  • packages/nextjs/CHANGELOG.md — line 11: the commit hash 69498df appears twice; remove the duplicate (or replace the second entry if a different commit was intended).
  • packages/nextjs/package.json — this package declares the four @clerk/* deps using the workspace protocol (value = "workspace:^"), so the changelog's explicit versions (2.9.0, 4.77.0, 3.20.1, 5.42.0) cannot be verified from that file. Confirm the actual versions in each package's own package.json (e.g., packages/backend/package.json, packages/types/package.json, packages/shared/package.json, packages/clerk-react/package.json) or via the published release tags.

Suggested CHANGELOG snippet with the duplicate removed:

- Updated dependencies [[`d400782`](https://github.com/clerk/javascript/commit/d400782b7016c1232c0aa1e3399c61b61e4f0709), [`69498df`](https://github.com/clerk/javascript/commit/69498dfca3e6bb388eb8c94313eac06347dd5a27), [`307dc3f`](https://github.com/clerk/javascript/commit/307dc3f05ba1bd3b30b491b198d9e65eebcc95f9), [`2db7431`](https://github.com/clerk/javascript/commit/2db743147827fb69fb8fe73a1e26545aeb7be7aa), [`59f1559`](https://github.com/clerk/javascript/commit/59f15593bab708b9e13eebfff6780c2d52b31b0a)]:
  - @clerk/[email protected]
  - @clerk/[email protected]
  - @clerk/[email protected]
  - @clerk/[email protected]

@LauraBeatris LauraBeatris reopened this Aug 14, 2025
@LauraBeatris LauraBeatris merged commit e4d7492 into main Aug 14, 2025
41 checks passed
@LauraBeatris LauraBeatris deleted the changeset-release/main branch August 14, 2025 13:11
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