Skip to content

ci(repo): Version packages #6481

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 8, 2025
Merged

ci(repo): Version packages #6481

merged 1 commit into from
Aug 8, 2025

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented Aug 6, 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

  • Add billing API for fetching available plans. (#6449) by @panteliselef

  • Adds machine-to-machine endpoints to the Backend SDK: (#6479) by @wobsoriano

    Note: Renamed from "machine_tokens" to "m2m_tokens" for clarity and consistency with canonical terminology. This avoids confusion with other machine-related concepts like machine secrets.

    Create M2M Tokens

    A machine secret is required when creating M2M tokens.

    const clerkClient = createClerkClient({
      machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY,
    });
    
    clerkClient.m2mTokens.create({
      // or pass as an option here
      // machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY
      secondsUntilExpiration: 3600,
    });

    Revoke M2M Tokens

    You can revoke tokens using either a machine secret or instance secret:

    // Using machine secret
    const clerkClient = createClerkClient({ machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY });
    clerkClient.m2mTokens.revoke({
      // or pass as an option here
      // machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY
      m2mTokenId: 'mt_xxxxx',
      revocationReason: 'Revoked by user',
    });
    
    // Using instance secret (default)
    const clerkClient = createClerkClient({ secretKey: 'sk_xxxx' });
    clerkClient.m2mTokens.revoke({
      m2mTokenId: 'mt_xxxxx',
      revocationReason: 'Revoked by user',
    });

    Verify M2M Tokens

    You can verify tokens using either a machine secret or instance secret:

    // Using machine secret
    const clerkClient = createClerkClient({ machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY });
    clerkClient.m2mTokens.verifySecret({
      // or pass as an option here
      // machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY
      secret: 'mt_secret_xxxxx',
    });
    
    // Using instance secret (default)
    const clerkClient = createClerkClient({ secretKey: 'sk_xxxx' });
    clerkClient.m2mTokens.verifySecret({
      secret: 'mt_secret_xxxxx',
    });

    To verify machine-to-machine tokens using when using authenticateRequest() with a machine secret, use the machineSecret option:

    const clerkClient = createClerkClient({
      machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY,
    });
    
    const authReq = await clerkClient.authenticateRequest(c.req.raw, {
      // or pass as an option here
      // machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY
      acceptsToken: 'm2m_token', // previously machine_token
    });
    
    if (authReq.isAuthenticated) {
      // ... do something
    }

Patch Changes

@clerk/[email protected]

Minor Changes

  • [Billing Beta] Update PlanDetailsProps to reflect that either planId or plan is allowed. (#6472) by @panteliselef

Patch Changes

@clerk/[email protected]

Minor Changes

  • [Billing Beta] Update PlanDetailsProps to reflect that either planId or plan is allowed. (#6472) by @panteliselef

Patch Changes

@clerk/[email protected]

Minor Changes

  • [Billing Beta] Update PlanDetailsProps to reflect that either planId or plan is allowed. (#6472) by @panteliselef

Patch Changes

@clerk/[email protected]

Minor Changes

  • [Billing Beta] Update PlanDetailsProps to reflect that either planId or plan is allowed. (#6472) by @panteliselef

Patch Changes

  • Introduce TaskChooseOrganization component which replaces TaskSelectOrganization with a new UI that make the experience similar to the previous SignIn and SignUp steps (#6446) by @LauraBeatris

  • [Experimental] Signals (#6450) by @dstaley

  • Rename task key from select-organization to choose-organization (#6482) by @LauraBeatris

@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

@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

    • Introduced a redesigned organization selection experience with the new TaskChooseOrganization component, providing a consistent UI with sign-in and sign-up steps.
    • Added support for machine-to-machine token creation by allowing the use of a machine secret key in various integrations.
    • Enhanced billing features with new plan details flexibility and a billing API for available plans.
    • Experimental Signals feature added.
  • Bug Fixes

    • Addressed a potential memory leak in telemetry collection.
  • Chores

    • Updated internal and external dependencies across multiple packages for improved stability and compatibility.

Copy link

vercel bot commented Aug 6, 2025

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

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 8, 2025 9:12am

Copy link

pkg-pr-new bot commented Aug 6, 2025

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/elements

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

@clerk/clerk-expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/clerk-react

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

@clerk/react-router

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

@clerk/remix

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/themes

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

@clerk/types

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

@clerk/upgrade

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

@clerk/vue

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

commit: f0ea6e1

Copy link
Contributor

coderabbitai bot commented Aug 6, 2025

📝 Walkthrough

Walkthrough

This pull request updates multiple @clerk packages by introducing a new component, TaskChooseOrganization, which replaces the previously existing TaskSelectOrganization component. The new component features a redesigned user interface that aligns the organization selection experience with the earlier SignIn and SignUp steps. The change is reflected in changelogs and version increments across several packages, including @clerk/clerk-react, @clerk/clerk-js, @clerk/nextjs, @clerk/react-router, @clerk/remix, @clerk/tanstack-react-start, @clerk/testing, and related localization and types packages. Additionally, patch-level dependency updates were applied across the affected packages.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • ci(repo): Version packages #6385: Adds the original TaskSelectOrganization component and related TypeScript types, which are directly related to this PR as it replaces that component with TaskChooseOrganization.

Suggested reviewers

  • LauraBeatris
  • panteliselef
  • wobsoriano
  • brkalow

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5bbf3eb and f0ea6e1.

📒 Files selected for processing (53)
  • .changeset/afraid-planets-fly.md (0 hunks)
  • .changeset/brown-garlics-boil.md (0 hunks)
  • .changeset/dull-cups-accept.md (0 hunks)
  • .changeset/hot-tables-worry.md (0 hunks)
  • .changeset/pink-countries-hunt.md (0 hunks)
  • .changeset/shaky-papers-push.md (0 hunks)
  • .changeset/shaky-sloths-unite.md (0 hunks)
  • .changeset/strong-chicken-lie.md (0 hunks)
  • .changeset/twenty-poems-push.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 (9)
  • .changeset/afraid-planets-fly.md
  • .changeset/twenty-poems-push.md
  • .changeset/shaky-papers-push.md
  • .changeset/dull-cups-accept.md
  • .changeset/strong-chicken-lie.md
  • .changeset/shaky-sloths-unite.md
  • .changeset/pink-countries-hunt.md
  • .changeset/brown-garlics-boil.md
  • .changeset/hot-tables-worry.md
✅ Files skipped from review due to trivial changes (10)
  • packages/remix/package.json
  • packages/vue/package.json
  • packages/react/package.json
  • packages/fastify/package.json
  • packages/testing/package.json
  • packages/localizations/package.json
  • packages/tanstack-react-start/package.json
  • packages/elements/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (34)
  • packages/shared/package.json
  • packages/clerk-js/package.json
  • packages/elements/package.json
  • packages/backend/package.json
  • packages/expo/package.json
  • packages/react-router/package.json
  • packages/types/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/astro/package.json
  • packages/agent-toolkit/package.json
  • packages/expo-passkeys/package.json
  • packages/express/package.json
  • packages/chrome-extension/package.json
  • packages/nuxt/package.json
  • packages/nextjs/package.json
  • packages/themes/package.json
  • packages/localizations/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/nextjs/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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
  • 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 src/utils.ts and explain its main purpose.
    • @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 comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

  • 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 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: 0

🧹 Nitpick comments (18)
packages/nextjs/package.json (1)

3-3: Confirm test coverage for the new TaskChooseOrganization flow

The 6.29.1 patch bump is fine, but the release introduces user-facing UI (the new component). Ensure there are E2E or component tests validating the new organisation-selection step across Next.js pages to avoid regressions.

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

3-11: Consider adding a release date for traceability

All previous entries omit dates, but including a short ISO-8601 date (e.g. “2025-08-14”) right after the version header makes it much easier to track when a patch landed across packages.

Example:

## 0.1.18 – 2025-08-14

No functional issues—purely a documentation nicety.

packages/express/CHANGELOG.md (1)

3-10: Include release date for consistency across changelogs

Adding the release date after the version (as suggested for other packages) improves auditability:

## 1.7.17 – 2025-08-14

Optional but recommended for downstream consumers who rely on changelog timelines.

packages/astro/CHANGELOG.md (1)

3-11: Consider adding context for the dependency bumps
The entry lists the updated internal packages, but a short phrase explaining why these bumps matter (e.g., “brings support for TaskChooseOrganization internals” or “syncs with latest core types”) would help downstream consumers decide whether to upgrade.

packages/backend/CHANGELOG.md (1)

3-10: Consider including a release date for traceability

Most sections list only the version header; adding the release date (e.g., ## 2.6.4 – 2025-08-14) improves auditability and keeps the changelog in line with common conventions.

packages/expo/CHANGELOG.md (1)

3-12: Add a short human-readable blurb before the dependency list

All earlier entries include a one-liner (e.g. “Patch Changes”) followed by a short sentence describing what changed.
For 2.14.16 we jump straight to the dependency list, which makes the log harder to skim. One sentence such as “Bumped internal Clerk packages to keep versions in sync with the monorepo” would restore consistency.

packages/nuxt/CHANGELOG.md (1)

3-12: Consider adding a release date for traceability

The new 1.8.3 entry follows the existing structure, but recording the release date (e.g. ## 1.8.3 – 2025-08-19) helps consumers quickly identify when a version became available and aligns with common changelog conventions.
No change is required if your team intentionally omits dates, but adding them can improve downstream auditing and debugging.

packages/localizations/CHANGELOG.md (1)

7-7: Singular agreement – “makes” instead of “make”
Subject-verb agreement is off here.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)
packages/react/CHANGELOG.md (1)

7-8: Grammar nit – singular/plural agreement

“…with a new UI that make the experience…” → should be “…with a new UI that makes the experience…”.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps
packages/testing/CHANGELOG.md (1)

7-8: Grammar nit – use singular verb agreement

Replace “make” with “makes” so the sentence reads smoothly.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)
packages/tanstack-react-start/CHANGELOG.md (2)

7-7: Grammar tweak: “makes” instead of “make”

Minor nit, but it reads more cleanly in the past‐tense bullet list.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps

9-13: Keep dependency list ordering consistent

Previous changelog sections list dependencies in a consistent (often alphabetical or “shared first”) order.
For readability and diff hygiene, consider aligning with that convention:

Totally optional, but it keeps the changelog uniform.

packages/types/CHANGELOG.md (1)

7-7: Minor grammar tweak – “make” → “makes”

The singular subject “UI” requires the verb “makes”.

- ...with a new UI that make the experience...
+ ...with a new UI that makes the experience...
packages/clerk-js/CHANGELOG.md (2)

7-8: Grammar fix: singular/verb agreement in the bullet description

“make the experience similar” → “makes the experience similar”

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)

3-6: Consider adding a release date for consistency

Previous entries commonly include a date next to the version header (e.g., ## 5.80.0 – 2025-07-22). Adding a date here improves traceability.

Example:

## 5.80.1 – 2025-08-14
packages/nextjs/CHANGELOG.md (1)

7-8: Minor grammar fix for clarity

In the description, replace “make” with “makes” so the verb agrees with the singular subject “component”.

- with a new UI that make the experience similar
+ with a new UI that makes the experience similar
packages/react-router/CHANGELOG.md (1)

7-7: Grammar tweak – “make” ➜ “makes”

Subject–verb agreement: the singular noun UI should take makes.

-- Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ...
+- Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ...
packages/remix/CHANGELOG.md (1)

7-8: Minor grammar fix for clarity

“make the experience similar” → “makes the experience similar” to keep subject-verb agreement.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ...
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ...
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1ad16da and 64e4eed.

📒 Files selected for processing (45)
  • .changeset/brown-garlics-boil.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 (1)
  • .changeset/brown-garlics-boil.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/express/package.json
  • packages/expo-passkeys/package.json
  • packages/expo/package.json
  • packages/themes/package.json
  • packages/chrome-extension/package.json
  • packages/types/package.json
  • packages/localizations/package.json
  • packages/remix/package.json
  • packages/nextjs/package.json
  • packages/nuxt/package.json
  • packages/tanstack-react-start/package.json
  • packages/shared/package.json
  • packages/elements/package.json
  • packages/testing/package.json
  • packages/fastify/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/react-router/package.json
  • packages/agent-toolkit/package.json
  • packages/elements/CHANGELOG.md
  • packages/react/package.json
  • packages/vue/package.json
  • packages/themes/CHANGELOG.md
  • packages/clerk-js/package.json
  • packages/types/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/backend/package.json
  • packages/astro/package.json
  • packages/localizations/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/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/express/package.json
  • packages/expo-passkeys/package.json
  • packages/expo/package.json
  • packages/themes/package.json
  • packages/chrome-extension/package.json
  • packages/types/package.json
  • packages/localizations/package.json
  • packages/remix/package.json
  • packages/nextjs/package.json
  • packages/nuxt/package.json
  • packages/tanstack-react-start/package.json
  • packages/shared/package.json
  • packages/elements/package.json
  • packages/testing/package.json
  • packages/fastify/package.json
  • packages/react-router/package.json
  • packages/agent-toolkit/package.json
  • packages/react/package.json
  • packages/vue/package.json
  • packages/clerk-js/package.json
  • packages/backend/package.json
  • packages/astro/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/express/package.json
  • packages/expo-passkeys/package.json
  • packages/expo/package.json
  • packages/themes/package.json
  • packages/chrome-extension/package.json
  • packages/types/package.json
  • packages/localizations/package.json
  • packages/remix/package.json
  • packages/nextjs/package.json
  • packages/nuxt/package.json
  • packages/tanstack-react-start/package.json
  • packages/shared/package.json
  • packages/elements/package.json
  • packages/testing/package.json
  • packages/fastify/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/react-router/package.json
  • packages/agent-toolkit/package.json
  • packages/elements/CHANGELOG.md
  • packages/react/package.json
  • packages/vue/package.json
  • packages/themes/CHANGELOG.md
  • packages/clerk-js/package.json
  • packages/types/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/backend/package.json
  • packages/astro/package.json
  • packages/localizations/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/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
packages/**/CHANGELOG.md

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

Maintain detailed changelogs

Files:

  • packages/expo-passkeys/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/themes/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/fastify/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). (5)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Build Packages
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (29)
packages/types/package.json (1)

3-3: Confirm SemVer suitability – new public component likely warrants a minor bump

A brand-new exported component (TaskChooseOrganization) is a user-facing feature, not a bug-fix. According to semantic-versioning, adding functionality in a backwards-compatible manner should increment the minor version, not the patch.

-  "version": "4.73.1",
+  "version": "4.74.0",

Please double-check that no consumers rely on version ranges like ^4.73.x, otherwise they won’t automatically receive the new feature.

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

3-3: LGTM – patch bump propagates internal dependency update

Patch increment to keep the package aligned with internal deps is correct; no further action required.

packages/shared/package.json (1)

3-3: LGTM – internal util package keeps pace with @clerk/types

Version bump is consistent with workspace constraints and causes no publish-time issues.

packages/themes/package.json (1)

3-3: LGTM – themes package correctly follows dependent type bump

Patch bump is appropriate since only transitive typings changed; build scripts remain untouched.

packages/remix/package.json (1)

3-3: LGTM – Remix SDK patch release aligns with dependency graph

Patch version aligns with downstream bumps and causes no API surface change here.

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

3-3: Patch bump and workspace dependency ranges look correct

0.1.18 is a semantic-version patch increment and keeps parity with the rest of the coordinated release. No further action needed.

packages/express/package.json (1)

3-3: Version increment aligns with semver

1.7.17 is an appropriate patch bump for downstream-only dependency updates. 👍

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

3-3: Patch bump looks good

1.8.11 correctly tracks the minor UI addition without a breaking change.

packages/nuxt/package.json (1)

3-3: Nuxt package patch bump acknowledged

1.8.3 is consistent with the multi-package release strategy. No issues spotted.

packages/backend/package.json (1)

3-3: Patch bump to 2.6.4 looks correct

The change follows semantic-versioning conventions and keeps the package in sync with the workspace. No additional action required.

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

3-3: Patch bump to 5.80.1 acknowledged

Version increment is appropriate for the contained dependency updates and new component exposure. No issues spotted.

packages/localizations/package.json (1)

3-3: Version updated to 3.20.8 — LGTM

Patch release aligns with the accompanying UI component addition. Looks good.

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

3-3: Increment to 0.21.7 is appropriate

Consistent with dependent package bumps; no further feedback.

packages/astro/package.json (1)

3-3: Patch bump to 2.10.15 verified

Maintains harmony with workspace dependency versions. Good to merge.

packages/elements/package.json (1)

3-3: Patch version bump is accurate and semver-compliant

0.23.490.23.50 is a correct patch increment for dependency-only updates.
No further action needed.

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

3-3: Version bump LGTM

The move from 2.5.16 to 2.5.17 follows semver patch rules. Nothing else changed in the manifest—good.

packages/expo/package.json (1)

3-3: Correct patch release

2.14.152.14.16 is appropriate for dependency refreshes only. ✅

packages/vue/package.json (1)

3-3: Patch bump acknowledged

1.9.21.9.3 maintains semver discipline. No additional feedback.

packages/themes/CHANGELOG.md (1)

3-9: Changelog entry structure is solid

– Version header, “Patch Changes” section, and dependency list are all present and correctly formatted.
– Link to the dependency update commit is included. Nice attention to detail.

packages/testing/package.json (1)

3-3: Patch version bump follows semver – looks good.
No additional concerns for this package manifest.

packages/react/package.json (2)

3-3: Patch version bump is correct, but ensure new component is covered by tests.

5.39.1 correctly reflects a patch‐level change.
However, the release introduces the new TaskChooseOrganization component (per PR description). I don’t see any corresponding tests added in this PR. Please add or update unit/integration tests to cover the new component’s rendering and behaviour.


3-3: Version bump itself LGTM.

packages/fastify/package.json (1)

3-3: Patch version bump is appropriate.
No other changes required.

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

3-10: Changelog entry is clear and follows existing style.

The new 0.3.27 section documents dependency bumps and links to the commit – consistent with previous entries.

packages/fastify/CHANGELOG.md (1)

3-10: Changelog entry looks good

The new 2.4.17 section follows the repo’s existing style (version heading, “Patch Changes”, dependency bullets with commit link) and contains all required details. No issues spotted.

packages/vue/CHANGELOG.md (1)

3-10: Changelog entry is well-formed and consistent

Version header, “Patch Changes” section, and dependency bump bullets follow the established style. No issues found.

packages/shared/CHANGELOG.md (1)

3-9: Changelog entry looks good

Version header, semantic-version bump, and dependency list follow the existing formatting conventions. No further action required.

packages/elements/CHANGELOG.md (1)

3-10: Changelog entry is well-formed and consistent

Header level, “Patch Changes” section, commit hash links, and dependency version bumps match the established pattern in earlier entries. No issues found.

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

3-10: Changelog entry looks good

Version header, section hierarchy, and dependency list follow the existing convention. No concerns.

Copy link
Contributor

coderabbitai bot commented Aug 6, 2025

📝 Walkthrough

Walkthrough

This change updates version numbers and changelogs across multiple packages, primarily to document dependency upgrades. A new component, TaskChooseOrganization, replaces the previous TaskSelectOrganization in several packages, with updates to the UI for organization selection to align with the SignIn and SignUp steps. The changes are reflected in changelog entries and package version bumps. No implementation or code logic changes are included in this diff; only documentation, changelog, and metadata files are modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • ci(repo): Version packages #6385: The main PR introduces the new TaskChooseOrganization component replacing TaskSelectOrganization, while the retrieved PR adds the original TaskSelectOrganization component and related types; thus, the main PR builds upon and is directly related to the changes in the retrieved PR.

Suggested reviewers

  • LauraBeatris
  • panteliselef

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
  • 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 src/utils.ts and explain its main purpose.
    • @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 comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

  • 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 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: 0

♻️ Duplicate comments (1)
packages/react-router/package.json (1)

3-3: Same semver concern as noted earlier

This package also surfaces the new TaskChooseOrganization feature; please verify whether a minor bump (1.9.0) is more accurate than a patch.
Tests for the new flow are missing as well.

-  "version": "1.8.11",
+  "version": "1.9.0",
🧹 Nitpick comments (15)
packages/types/CHANGELOG.md (1)

7-7: Typo – use singular verb “makes”

“...a new UI that make the experience...” → should read “makes”.
Consistency with previous entries keeps the changelog polished.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps
packages/vue/CHANGELOG.md (1)

3-10: Consider stamping release date in the heading
Including the release date (e.g. ## 1.9.3 – 2025-08-??) makes it easier for consumers to trace changes chronologically.

packages/shared/CHANGELOG.md (1)

3-9: Clarify the user-visible impact of the patch

The entry currently only states that dependencies were updated. Adding a short note such as “No runtime or API changes – package behavior remains unchanged” will make the intent clearer to consumers scanning the changelog.

packages/fastify/CHANGELOG.md (1)

3-10: Clarify that this release only bumps internal peer-deps

The 2.4.17 note lists dependency bumps but doesn’t explicitly state that there are no runtime/API changes for @clerk/fastify itself. A short sentence such as “No functional changes were made in this package” helps consumers quickly understand impact.

 ## 2.4.17

 ### Patch Changes
-- Updated dependencies [[`1ad16da`](https://github.com/clerk/javascript/commit/1ad16daa49795a861ae277001831230580b6b9f4)]:
+- Updated dependencies [[`1ad16da`](https://github.com/clerk/javascript/commit/1ad16daa49795a861ae277001831230580b6b9f4)] – no runtime changes in this package:
packages/chrome-extension/CHANGELOG.md (1)

7-10: Consider surfacing noteworthy upstream changes for better traceability
Since @clerk/[email protected] introduces the new TaskChooseOrganization component, adding a short note (e.g. “inherits new TaskChooseOrganization UI from clerk-js”) would help consumers quickly see functional impact beyond plain version bumps.

packages/localizations/CHANGELOG.md (1)

7-8: Minor grammar tweak – “make” → “makes”

The sentence “with a new UI that make the experience similar…” should use “makes” so that the verb agrees with “UI”.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps
packages/testing/CHANGELOG.md (2)

7-7: Fix grammatical agreement in description

“…a new UI that make the experience…” → should read “…a new UI that makes the experience…”.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ...
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ...

7-8: Add migration hint for downstream consumers

Since TaskSelectOrganization is replaced, a brief note guiding users on how to update existing tests that rely on the removed helper would be helpful.
Example: “Rename imports of TaskSelectOrganization to TaskChooseOrganization.”

packages/react/CHANGELOG.md (1)

7-7: Grammar: use singular verb “makes”.

In the sentence “with a new UI that make the experience similar”, the subject “UI” is singular, so the verb should be “makes”.

- with a new UI that make the experience similar
+ with a new UI that makes the experience similar
packages/remix/CHANGELOG.md (2)

7-8: Grammar: use singular verb “makes”
“…with a new UI that make the experience…” → should be “makes the experience”.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps

9-14: Bullet-list style not aligned with previous entries
Prior dependency sections indent list items two spaces after the dash. These four items are flush with the dash, breaking consistency. Re-indent to keep the changelog uniform.

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

7-8: Grammar tweak for clarity

Minor wording issue – “make” should be “makes”.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the earlier `SignIn` and `SignUp` steps
packages/clerk-js/CHANGELOG.md (1)

7-8: Fix subject-verb agreement (“make” → “makes”).

Minor grammar tweak for clarity and consistency.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ([#6446](https://github.com/clerk/javascript/pull/6446)) by [@LauraBeatris](https://github.com/LauraBeatris)
packages/tanstack-react-start/CHANGELOG.md (1)

7-8: Grammar tweak – use singular verb “makes”

“…with a new UI that makes the experience similar…” reads grammatically better than “…that make…”.

- - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps ...
+ - Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps ...
packages/nextjs/CHANGELOG.md (1)

7-8: Fix grammatical agreement in bullet

“make the experience” should be singular (“makes”) to match the singular subject (“a new UI”).

- Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that make the experience similar to the previous `SignIn` and `SignUp` steps
+ Introduce `TaskChooseOrganization` component which replaces `TaskSelectOrganization` with a new UI that makes the experience similar to the previous `SignIn` and `SignUp` steps
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1ad16da and 64e4eed.

📒 Files selected for processing (45)
  • .changeset/brown-garlics-boil.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 (1)
  • .changeset/brown-garlics-boil.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/express/package.json
  • packages/expo-passkeys/package.json
  • packages/backend/package.json
  • packages/remix/package.json
  • packages/themes/package.json
  • packages/astro/package.json
  • packages/react-router/package.json
  • packages/testing/package.json
  • packages/shared/package.json
  • packages/fastify/package.json
  • packages/elements/package.json
  • packages/types/package.json
  • packages/clerk-js/package.json
  • packages/themes/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/vue/package.json
  • packages/vue/CHANGELOG.md
  • packages/localizations/package.json
  • packages/astro/CHANGELOG.md
  • packages/tanstack-react-start/package.json
  • packages/agent-toolkit/package.json
  • packages/chrome-extension/package.json
  • packages/nuxt/package.json
  • packages/expo/package.json
  • packages/react/package.json
  • packages/shared/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/nextjs/package.json
  • packages/agent-toolkit/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/chrome-extension/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/express/package.json
  • packages/expo-passkeys/package.json
  • packages/backend/package.json
  • packages/remix/package.json
  • packages/themes/package.json
  • packages/astro/package.json
  • packages/react-router/package.json
  • packages/testing/package.json
  • packages/shared/package.json
  • packages/fastify/package.json
  • packages/elements/package.json
  • packages/types/package.json
  • packages/clerk-js/package.json
  • packages/vue/package.json
  • packages/localizations/package.json
  • packages/tanstack-react-start/package.json
  • packages/agent-toolkit/package.json
  • packages/chrome-extension/package.json
  • packages/nuxt/package.json
  • packages/expo/package.json
  • packages/react/package.json
  • packages/nextjs/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/express/package.json
  • packages/expo-passkeys/package.json
  • packages/backend/package.json
  • packages/remix/package.json
  • packages/themes/package.json
  • packages/astro/package.json
  • packages/react-router/package.json
  • packages/testing/package.json
  • packages/shared/package.json
  • packages/fastify/package.json
  • packages/elements/package.json
  • packages/types/package.json
  • packages/clerk-js/package.json
  • packages/themes/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/vue/package.json
  • packages/vue/CHANGELOG.md
  • packages/localizations/package.json
  • packages/astro/CHANGELOG.md
  • packages/tanstack-react-start/package.json
  • packages/agent-toolkit/package.json
  • packages/chrome-extension/package.json
  • packages/nuxt/package.json
  • packages/expo/package.json
  • packages/react/package.json
  • packages/shared/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/nextjs/package.json
  • packages/agent-toolkit/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
packages/**/CHANGELOG.md

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

Maintain detailed changelogs

Files:

  • packages/themes/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/chrome-extension/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). (22)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (tanstack-react-router, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Publish with pkg-pr-new
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: Unit Tests (18, --filter=@clerk/astro --filter=@clerk/backend --filter=@clerk/express --filter=@c...
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (32)
packages/types/package.json (1)

3-3: Patch bump follows semver & package-naming rules – LGTM

The update from 4.73.04.73.1 is a correct patch bump for a non-breaking change, and the package remains under packages/ with the @clerk namespace, satisfying the repo’s publishing guidelines.
No further action required.

packages/themes/package.json (1)

3-3: Version bump consistent with dependent workspace range

2.4.52.4.6 is an appropriate patch increment and still aligns with the workspace-scoped dependency on @clerk/types (workspace:^).
Everything else stays unchanged, so nothing blocking merge.

packages/remix/package.json (1)

3-3: Patch version bump looks correct
The increment from 4.10.104.10.11 follows SemVer for a patch-level change. No further concerns.

packages/elements/package.json (1)

3-3: SemVer compliance confirmed
Version update to 0.23.50 is an appropriate patch bump for dependency updates only.

packages/fastify/package.json (1)

3-3: Version bump LGTM
2.4.162.4.17 is a proper patch increment matching the dependency refresh.

packages/localizations/package.json (1)

3-3: Patch release validated
3.20.73.20.8 adheres to semantic versioning; no additional issues detected.

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

3-3: Patch version increment acknowledged
Moving to 0.1.18 is consistent with a non-breaking dependency update.

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

3-3: Confirm semver bump & add tests for the new component

TaskChooseOrganization is a new, user-visible feature. Under semantic-versioning this usually warrants a minor bump (0.22.0) rather than a patch.
Please confirm the change-level and adjust if needed.
Also, no tests were added for the new step – consider adding at least one UI/integration test to cover it.

-  "version": "0.21.7",
+  "version": "0.22.0",
packages/shared/package.json (1)

3-3: LGTM – internal patch looks correct

Only internal utilities bumped; a patch release is appropriate and everything else complies with publishing guidelines.

packages/nuxt/package.json (1)

3-3: LGTM – patch bump is appropriate

No public API additions inside this package; a patch update to 1.8.3 is correct.

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

3-3: LGTM – patch bump is appropriate

Pure dependency alignment; the version increment to 0.3.27 is fine.

packages/expo/package.json (1)

3-3: Version bump looks correct
Patch‐level increment from 2.14.15 → 2.14.16 keeps semver hygiene and aligns with the other packages in this release set.

packages/express/package.json (1)

3-3: Patch version bump acknowledged
1.7.16 → 1.7.17 follows semver and requires no further action.

packages/vue/package.json (1)

3-3: Vue SDK patch bump is fine
1.9.2 → 1.9.3 correctly conveys a non-breaking dependency update.

packages/backend/package.json (1)

3-3: Backend SDK patch bump approved
2.6.3 → 2.6.4 is consistent with dependency updates; no issues spotted.

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

3-3: SemVer-correct patch bump looks good

The jump from 5.80.0 → 5.80.1 follows semantic-versioning rules for a patch release. No further action needed.

packages/testing/package.json (1)

3-3: Patch version increment is appropriate

1.10.10 → 1.10.11 is correctly scoped as a patch. Changelog already covers the dependency bump. LGTM.

packages/astro/package.json (1)

3-3: Version bump confirmed

2.10.14 → 2.10.15 is a patch; no other manifest changes. ✔️

packages/nextjs/package.json (1)

3-3: NextJS package patch bump acknowledged

6.29.0 → 6.29.1 is semver-compliant. Ensure the new TaskChooseOrganization component is covered by existing integration tests in this repo.

packages/themes/CHANGELOG.md (1)

3-9: Changelog entry is concise and satisfies guidelines

The 2.4.6 section clearly lists the dependency update with a commit reference. Nice work keeping the history exhaustive.

packages/react/package.json (1)

3-3: Patch version bump looks good

5.39.0 → 5.39.1 follows semver and matches the coordinated release notes.

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

3-3: Patch version bump confirmed

2.5.16 → 2.5.17 is an appropriate patch increment for dependency‐only changes.

packages/astro/CHANGELOG.md (1)

3-11: Changelog entry is clear and compliant

New section ## 2.10.15 accurately describes the dependency updates and links to the commit.

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

3-10: Changelog entry LGTM
Entry follows the established style for automated patch releases; no issues found.

packages/elements/CHANGELOG.md (1)

3-11: Changelog entry meets repo conventions

Header, version number, and dependency bumps are clearly documented and consistent with prior entries. No action required.

packages/nuxt/CHANGELOG.md (1)

3-11: Changelog entry looks solid

The new 1.8.3 section adheres to the existing format: proper heading hierarchy, “Patch Changes” sub-heading, and dependency list with commit reference. No discrepancies spotted.

packages/express/CHANGELOG.md (1)

3-10: Changelog entry is consistent and complete – looks good.
The version header, sub-section, and dependency list follow the existing conventions. No further action needed.

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

3-10: Changelog entry looks complete and correctly formatted
The new patch section lists all bumped dependencies with commit links and follows the existing style. No further action required.

packages/backend/CHANGELOG.md (1)

3-10: Changelog entry looks correct and well-formatted

The new 2.6.4 section follows the existing structure, includes a heading and dependency bump list, and respects Markdown conventions. No action needed.

packages/expo/CHANGELOG.md (1)

3-11: Add a concise description for easier scanning

All previous entries briefly mention what the dependency bumps deliver (e.g. “Updated dependencies …”).
Consider adding one-liner context such as:

## 2.14.16
### Patch Changes
- Align Expo with TaskChooseOrganization introduction (dependency bumps only)

That gives readers skimming the CHANGELOG immediate insight without having to expand commit links.
[ suggest_nitpick ]

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

3-10: Changelog entry format and content look correct
Header hierarchy, versioning, and dependency bullets follow the project’s existing convention – no issues spotted.

packages/localizations/CHANGELOG.md (1)

3-11: Changelog entry looks good overall

Version header, “Patch Changes” subsection, bullet formatting, and dependency list all follow the project’s existing conventions. No structural issues spotted.

@nikosdouvlis nikosdouvlis merged commit cf284ee into main Aug 8, 2025
109 of 112 checks passed
@nikosdouvlis nikosdouvlis deleted the changeset-release/main branch August 8, 2025 13:43
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