Skip to content

ci(repo): Version packages #6377

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
Jul 24, 2025
Merged

ci(repo): Version packages #6377

merged 1 commit into from
Jul 24, 2025

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented Jul 23, 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

  • [Billing Beta] Introduce top level subscription. (#6317) by @panteliselef

    Updated CommerceSubscriptionJSON to describe the top level subscription and renamed the existing type to CommerceSubscriptionItemJSON.
    Deprecated billing.getSubscriptions() in favour of billing.getSubscription.

  • [Billing Beta] Replace useSubscriptionItems with useSubscription. (#6317) by @panteliselef

Patch Changes

@clerk/[email protected]

Minor Changes

  • Expose <CheckoutButton/>, <SubscriptionDetailsButton/>, <PlanDetailsButton/> from @clerk/nextjs/experimental. (#6365) by @panteliselef

Patch Changes

@clerk/[email protected]

Minor Changes

  • Expose <CheckoutButton/>, <SubscriptionDetailsButton/>, <PlanDetailsButton/> from @clerk/clerk-react/experimental. (#6365) by @panteliselef

Patch Changes

@clerk/[email protected]

Minor Changes

  • [Billing Beta] Replace useSubscriptionItems with useSubscription. (#6317) by @panteliselef

Patch Changes

@clerk/[email protected]

Minor Changes

  • [Billing Beta] Introduce top level subscription. (#6317) by @panteliselef

    Updated CommerceSubscriptionJSON to describe the top level subscription and renamed the existing type to CommerceSubscriptionItemJSON.
    Deprecated billing.getSubscriptions() in favour of billing.getSubscription.

@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 new experimental components: <CheckoutButton/>, <SubscriptionDetailsButton/>, and <PlanDetailsButton/> in select packages.
    • Improved machine authentication verification in API routes for Next.js.
  • Improvements

    • Updated billing features with a new top-level subscription concept and updated related methods and hooks.
    • Deprecated some older billing methods in favor of streamlined alternatives.
  • Chores

    • Updated internal dependencies across multiple packages for improved stability and compatibility.
    • Incremented package versions to reflect the latest updates.

Copy link

vercel bot commented Jul 23, 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 Jul 23, 2025 7:52pm

Copy link

pkg-pr-new bot commented Jul 23, 2025

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/elements

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

@clerk/clerk-expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/clerk-react

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

@clerk/react-router

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

@clerk/remix

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/themes

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

@clerk/types

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

@clerk/upgrade

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

@clerk/vue

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

commit: 7244332

Copy link
Contributor

coderabbitai bot commented Jul 23, 2025

📝 Walkthrough

"""

Walkthrough

This change set consists of version bumps and changelog updates across multiple packages. The updates primarily document dependency upgrades, especially for the @clerk/types package (to version 4.70.0) and related packages such as @clerk/shared, @clerk/backend, and others. Additionally, the Billing Beta feature introduces a top-level subscription concept, with associated type renaming and API deprecations noted in changelogs. Two changeset markdown files documenting minor updates to subscription hooks and experimental components were removed. No source code or functional logic is modified; the changes are confined to changelog files, package metadata, and the removal of changelog entries.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Suggested labels

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

Suggested reviewers

  • aeliox
  • panteliselef
  • LauraBeatris
    """

📜 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 067747c and 7244332.

📒 Files selected for processing (48)
  • .changeset/curly-jeans-sleep.md (0 hunks)
  • .changeset/dark-coins-shake.md (0 hunks)
  • .changeset/rare-readers-cough.md (0 hunks)
  • .changeset/wide-loops-decide.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 (4)
  • .changeset/rare-readers-cough.md
  • .changeset/dark-coins-shake.md
  • .changeset/curly-jeans-sleep.md
  • .changeset/wide-loops-decide.md
✅ Files skipped from review due to trivial changes (13)
  • packages/themes/package.json
  • packages/backend/package.json
  • packages/expo/package.json
  • packages/testing/package.json
  • packages/fastify/package.json
  • packages/tanstack-react-start/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/vue/package.json
  • packages/nuxt/package.json
  • packages/express/CHANGELOG.md
  • packages/expo/CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (30)
  • packages/expo-passkeys/package.json
  • packages/elements/package.json
  • packages/astro/package.json
  • packages/localizations/package.json
  • packages/clerk-js/package.json
  • packages/shared/package.json
  • packages/types/package.json
  • packages/react/package.json
  • packages/remix/package.json
  • packages/express/package.json
  • packages/themes/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/react-router/package.json
  • packages/backend/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/nextjs/package.json
  • packages/agent-toolkit/package.json
  • packages/testing/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
  • packages/elements/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/chrome-extension/package.json
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/chrome-extension/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.

Whenever reviewing a pull request, if there are any changes that could impact security, always tag clerk/security in the PR.

Security-impacting changes include, but are not limited to:

  • Changes to authentication logic or mechanisms (e.g. login, session handling, token issuance)
  • Any modification to access control, authorization checks, or role-based permissions
  • Introduction or modification of hashing algorithms, signature verification, or cryptographic primitives
  • Handling of sensitive data (e.g. passwords, tokens, secrets, PII)
  • Integration with external identity providers (e.g. SSO, OAuth, OpenID Connect)
  • Modifications to security headers, cookie flags, CORS policies, or CSRF protections
  • Bypass mechanisms (e.g. feature flags, testing overrides) that could weaken protections
  • Changes to rate limiting, abuse prevention, or input validation

If you're unsure whether a change is security-relevant, err on the side of caution and tag clerk/security.

Any time that you tag clerk/security, please do so explicitly in a code comment, rather than within a collapsed section in a coderabbit comment, such as the "recent review details" section. If you do use the team name in any thinking or non-direct-code-comment content, it can be referred to as "clerk security team" to avoid accidentally printing the tag which sends a notification to the team.

Files:

  • packages/chrome-extension/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: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (1)
packages/chrome-extension/package.json (1)

3-3: Version bump follows semver and package-naming guidelines
Patch update from 2.5.112.5.12 is appropriate for internal dependency refresh; no other metadata changes needed.


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.
    • @coderabbitai modularize this function.
  • 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.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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 (24)
packages/expo/package.json (1)

3-3: Patch bump looks correct; remember the changelog

2.14.10 → 2.14.11 is a straight patch. Make sure packages/expo/CHANGELOG.md (usually auto-generated by Changesets) reflects this so consumers know why they’re upgrading.

packages/shared/package.json (1)

3-3: Minor bump acknowledged; refresh lockfile after merge

After merging, run the workspace install to propagate @clerk/[email protected] into pnpm-lock.yaml so downstream consumers get the new version.

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

3-3: Patch-level bump looks correct; verify accompanying CHANGELOG entry.

2.5.11 → 2.5.12 is a semantic-versioning-compliant patch upgrade that syncs with dependency bumps across the workspace. Just double-check that packages/chrome-extension/CHANGELOG.md (or the monorepo root changelog) includes a corresponding entry so consumers see the update rationale.

packages/react/CHANGELOG.md (1)

3-10: Changelog entry looks good – consider adding a date for uniformity

Everything follows the existing format.
If prior sections normally include a release date, appending one here (e.g. ## 5.35.5 – 2025-07-xx) would keep the file stylistically consistent.

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

3-10: Clarify whether any runtime impact exists

The entry only lists dependency bumps. To help consumers quickly assess impact, add an explicit note such as “No runtime-level changes; this release only updates internal @clerk/* dependencies.”

 ## 0.3.22
 ### Patch Changes
+- No runtime changes; aligns dependencies with the rest of the monorepo.
packages/vue/CHANGELOG.md (1)

3-10: Add an explicit “no functional changes” note

Consider appending a brief sentence so users know this patch is dependency-only.

 ## 1.8.20
 ### Patch Changes
 - Updated dependencies [...]
   - @clerk/[email protected]
   - @clerk/[email protected]
+  - No functional changes in @clerk/vue.
packages/fastify/CHANGELOG.md (1)

7-8: Deduplicate commit reference in dependency list

Commit hash cd59c0e is listed twice. Keeping a single reference is cleaner and consistent with earlier entries.

- - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
packages/nuxt/CHANGELOG.md (1)

7-11: Remove duplicated commit hash in dependency list

The same commit hash cd59c0e is listed twice. Keeping a single reference is cleaner and avoids the impression that two distinct changes occurred.

- - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
packages/express/CHANGELOG.md (1)

7-9: Duplicate commit hash reference – consider trimming to one link

The square-bracket list shows the same commit hash (cd59c0e...) twice. Unless two different commits were intended, keeping both links adds noise.

- Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
packages/astro/CHANGELOG.md (1)

7-10: Remove the duplicated commit reference to keep the changelog tidy

The same commit hash cd59c0e is listed twice in the “Updated dependencies” bracket list. One is enough.

- - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
packages/react-router/CHANGELOG.md (1)

7-8: Duplicate commit hash in dependency bullet – remove redundancy
The same commit hash cd59c0e is listed twice inside the square-bracket link array. One entry is enough.

- - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:

Tidying this up keeps the changelog concise and avoids confusion.

packages/expo/CHANGELOG.md (2)

3-12: Enrich the changelog entry with a concise description of the effect of the bump

The entry for 2.14.11 only lists dependency bumps. Given the guidelines that package changelogs should stay “detailed”, add a short sentence explaining why the bump matters (e.g. “syncs with Billing Beta top-level subscription changes”) so that consumers don’t have to inspect every downstream package.


7-8: Remove the duplicated commit hash

cd59c0e appears twice in the “Updated dependencies” list. Kill the duplicate to avoid noise.

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

7-11: Avoid repeating the same commit hash in the “Updated dependencies” list

The same commit (cd59c0e) is listed twice in the bullet. Tidying this up keeps the changelog compact and easier to scan.

- - Updated dependencies [[`cd59c0e`...], [`cd59c0e`...]]:
+ - Updated dependencies [[`cd59c0e`...]]:

Please also verify that the corresponding package.json reflects these exact dependency versions.

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

7-11: Deduplicate the commit reference for clarity

As above, the same commit hash appears twice in the bracket list. One entry is sufficient.

- - Updated dependencies [[`cd59c0e`...], [`cd59c0e`...]]:
+ - Updated dependencies [[`cd59c0e`...]]:

Confirm that package.json for @clerk/agent-toolkit is bumped to the same dependency versions to keep everything in sync.

packages/elements/CHANGELOG.md (1)

7-10: Remove duplicate commit hash entry for clarity
The same commit hash (cd59c0e) appears twice in the brackets. One occurrence is sufficient and keeps the changelog concise.

- - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
packages/testing/CHANGELOG.md (1)

7-7: Duplicate commit hash reference – drop the second link

The “Updated dependencies” bullet shows the same commit (cd59c0e) twice. One reference is enough and keeps the changelog tidy.

packages/backend/CHANGELOG.md (1)

3-10: Add release date and remove duplicate commit hash

  1. We normally suffix the header with the publication date for easier history scanning.
  2. The same commit hash (cd59c0e) appears twice in the dependency bullet – one entry is enough.
-## 2.5.2
-### Patch Changes
-- Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+## 2.5.2 – 2025-07-XX
+### Patch Changes
+- Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:

This keeps the changelog concise and consistent.

packages/shared/CHANGELOG.md (1)

3-13: Expand the 3.15.0 entry for completeness

The note only references the React hook rename, but the same release implicitly relies on the new top-level CommerceSubscriptionJSON concept and the deprecation of billing.getSubscriptions(). Mentioning these here (or linking to the @clerk/types changelog) will save consumers a trip across packages and keeps this changelog self-contained.

Optionally, add the release date to stay in line with many OSS changelog conventions.

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

7-7: Duplicated commit hash in bullet list

The same commit cd59c0e is referenced twice in the dependency-update bullet. Unless this is intentional (e.g. multiple packages released off the same commit), consider removing the duplicate to keep the changelog concise.

packages/nextjs/CHANGELOG.md (1)

7-11: Duplicate commit hash in the bullet list

The two commit hashes inside the square brackets are identical (cd59c0e…). Unless both entries intentionally point to different changesets that happen to share the same hash prefix (highly unlikely), one of them can be safely removed to reduce noise.

- - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:

Minor but keeps the changelog concise.

packages/remix/CHANGELOG.md (2)

7-11: Avoid duplicate commit references in the same bullet

The square-bracket list repeats the exact commit hash cd59c0e twice, which adds noise and slightly bloats the generated changelog.
Unless there really are two distinct commits with identical hashes (unlikely), keep only one reference.

- - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5), [`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:
+ - Updated dependencies [[`cd59c0e`](https://github.com/clerk/javascript/commit/cd59c0e5512a341dd8fb420aca583333c8243aa5)]:

3-6: Heading spacing looks off compared to previous entries

Older entries separate the version header from the “Patch Changes” header by an empty line (see e.g. 4.10.5).
For 4.10.6 there are two empty lines, which breaks the visual rhythm. Consider aligning the spacing for consistency.

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

3-20: Add release date to header for consistency

Most other packages in the repo include the release date after the version header (e.g. ## 5.75.0 – 2024-07-02).
Adding the date here helps readers quickly contextualize the release timeline and keeps the changelog formatting uniform.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cd59c0e and 53a30ff.

📒 Files selected for processing (46)
  • .changeset/rare-readers-cough.md (0 hunks)
  • .changeset/wide-loops-decide.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)
📓 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/expo-passkeys/package.json
  • packages/react-router/package.json
  • packages/fastify/package.json
  • packages/nextjs/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/testing/package.json
  • packages/themes/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/express/package.json
  • packages/elements/package.json
  • packages/chrome-extension/package.json
  • packages/agent-toolkit/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/themes/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/tanstack-react-start/package.json
  • packages/vue/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/clerk-js/package.json
  • packages/react/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/remix/package.json
  • packages/types/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/shared/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/nextjs/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/expo-passkeys/package.json
  • packages/react-router/package.json
  • packages/fastify/package.json
  • packages/nextjs/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/testing/package.json
  • packages/themes/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/express/package.json
  • packages/elements/package.json
  • packages/chrome-extension/package.json
  • packages/agent-toolkit/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/tanstack-react-start/package.json
  • packages/clerk-js/package.json
  • packages/remix/package.json
  • packages/shared/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.

Whenever reviewing a pull request, if there are any changes that could impact security, always tag clerk/security in the PR.

Security-impacting changes include, but are not limited to:

  • Changes to authentication logic or mechanisms (e.g. login, session handling, token issuance)
  • Any modification to access control, authorization checks, or role-based permissions
  • Introduction or modification of hashing algorithms, signature verification, or cryptographic primitives
  • Handling of sensitive data (e.g. passwords, tokens, secrets, PII)
  • Integration with external identity providers (e.g. SSO, OAuth, OpenID Connect)
  • Modifications to security headers, cookie flags, CORS policies, or CSRF protections
  • Bypass mechanisms (e.g. feature flags, testing overrides) that could weaken protections
  • Changes to rate limiting, abuse prevention, or input validation

If you're unsure whether a change is security-relevant, err on the side of caution and tag clerk/security.

Any time that you tag clerk/security, please do so explicitly in a code comment, rather than within a collapsed section in a coderabbit comment, such as the "recent review details" section. If you do use the team name in any thinking or non-direct-code-comment content, it can be referred to as "clerk security team" to avoid accidentally printing the tag which sends a notification to the team.

Files:

  • packages/expo-passkeys/package.json
  • packages/react-router/package.json
  • packages/fastify/package.json
  • packages/nextjs/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/testing/package.json
  • packages/themes/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/express/package.json
  • packages/elements/package.json
  • packages/chrome-extension/package.json
  • packages/agent-toolkit/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/themes/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/tanstack-react-start/package.json
  • packages/vue/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/clerk-js/package.json
  • packages/react/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/remix/package.json
  • packages/types/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/shared/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/nextjs/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/themes/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/vue/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/react/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/types/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/expo-passkeys/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/nextjs/CHANGELOG.md
  • packages/clerk-js/CHANGELOG.md
💤 Files with no reviewable changes (2)
  • .changeset/wide-loops-decide.md
  • .changeset/rare-readers-cough.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/expo-passkeys/package.json
  • packages/react-router/package.json
  • packages/fastify/package.json
  • packages/nextjs/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/testing/package.json
  • packages/themes/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/express/package.json
  • packages/elements/package.json
  • packages/chrome-extension/package.json
  • packages/agent-toolkit/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/themes/CHANGELOG.md
  • packages/astro/CHANGELOG.md
  • packages/nuxt/CHANGELOG.md
  • packages/agent-toolkit/CHANGELOG.md
  • packages/react-router/CHANGELOG.md
  • packages/tanstack-react-start/package.json
  • packages/vue/CHANGELOG.md
  • packages/tanstack-react-start/CHANGELOG.md
  • packages/clerk-js/package.json
  • packages/react/CHANGELOG.md
  • packages/localizations/CHANGELOG.md
  • packages/remix/package.json
  • packages/types/CHANGELOG.md
  • packages/shared/CHANGELOG.md
  • packages/backend/CHANGELOG.md
  • packages/shared/package.json
  • packages/expo-passkeys/CHANGELOG.md
  • packages/fastify/CHANGELOG.md
  • packages/express/CHANGELOG.md
  • packages/testing/CHANGELOG.md
  • packages/elements/CHANGELOG.md
  • packages/chrome-extension/CHANGELOG.md
  • packages/remix/CHANGELOG.md
  • packages/expo/CHANGELOG.md
  • packages/nextjs/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/expo-passkeys/package.json
  • packages/react-router/package.json
  • packages/fastify/package.json
  • packages/nextjs/package.json
  • packages/backend/package.json
  • packages/react/package.json
  • packages/testing/package.json
  • packages/themes/package.json
  • packages/expo/package.json
  • packages/nuxt/package.json
  • packages/express/package.json
  • packages/elements/package.json
  • packages/chrome-extension/package.json
  • packages/agent-toolkit/package.json
  • packages/astro/package.json
  • packages/vue/package.json
  • packages/localizations/package.json
  • packages/types/package.json
  • packages/tanstack-react-start/package.json
  • packages/clerk-js/package.json
  • packages/remix/package.json
  • packages/shared/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.

Whenever reviewing a pull request, if there are any changes that could impact security, always tag clerk/security in the PR.

Security-impacting changes include, but are not limited to:

  • Changes to authentication logic or mechanisms (e.g. login, session handling, token issuance)
  • Any modification to access control, authorization checks, or role-based permissions
  • Introduction or modification of hashing algorithms, signature verification, or cryptographic primitives
  • Handling of sensitive data (e.g. passwords, tokens, secrets, PII)
  • Integration with external identity providers (e.g. SSO, OAuth, OpenID Connect)
  • Modifications to security headers, cookie flags, CORS policies, or CSRF protections
  • Bypass mechanisms (e.g. feature flags, testing overrides) that could weaken protections
  • Changes to rate limiting, abuse prevention, or input validation

If you're unsure whether a change is security-relevant, err on the side of caution and tag clerk/security.

Any time that you tag clerk/security, please do so explicitly in a code comment, rather than within a collapsed section in a coderabbit comment, such as the "recent review details" section. If you do use the team name in any thinking or non-direct-code-comment content, it can be referred to as "clerk security team" to avoid accidentally printing the tag which sends a notification to the team.

Files:

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

3-3: Version bump LGTM

Patch increment follows semver; no other manifest changes.

packages/themes/package.json (1)

3-3: Patch release version is appropriate

2.4.0 → 2.4.1 properly reflects a non-breaking internal dependency update.

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

3-3: Semver patch bump looks correct

No additional manifest changes detected; package path and namespace comply with guidelines.

packages/testing/package.json (1)

3-3: Testing package patch bump acknowledged

1.10.5 → 1.10.6 maintains semver consistency across workspace.

packages/fastify/package.json (1)

3-3: Fastify SDK patch bump verified

Change aligns with internal dependency updates; nothing else to flag.

packages/elements/package.json (1)

3-3: Patch bump is appropriate and consistent with semver

Only dependency updates were introduced; a 0.0.1 increment is correct.
No other concerns.

packages/nuxt/package.json (1)

3-3: Patch version increment looks correct

The change is limited to internal-dependency bumps; sticking to 1.7.x is semver-compliant.
Everything else remains unchanged.

packages/backend/package.json (1)

3-3: LGTM – patch release makes sense

Nothing besides workspace dependency updates changed.
Version 2.5.2 accurately reflects a non-breaking patch.

packages/localizations/package.json (1)

3-3: Patch bump accepted

No functional changes beyond bumping @clerk/types; a 0.0.1 increment is correct.
File is otherwise untouched.

packages/types/package.json (1)

3-3: Minor version bump (4.69.04.70.0) is justified

New non-breaking typings and deprecations warrant a minor increment.
Changelog entry already present; no further action required.

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

3-3: Minor bump aligns with new Billing APIs—sanity-check dependents & docs

Going from 5.75.x to 5.76.0 is SemVer-minor and introduces new subscription helpers (billing.getSubscription, useSubscription).
Please verify:
• All internal packages using workspace:^ resolve to 5.76.0.
• Public docs & examples have been updated away from deprecated methods/hooks.
No code issues spotted—just a release-readiness check.

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

3-3: Patch increment is consistent with dependency bumps

0.21.1 → 0.21.2 looks good and keeps SemVer contract intact.

packages/nextjs/package.json (1)

3-3: Patch bump OK; peer range still valid

6.25.5 → 6.25.6 poses no compatibility concerns; the existing peer range for Next.js already covers current versions.

packages/express/package.json (1)

3-3: Version bump looks good

Patch bump 1.7.11 → 1.7.12 is consistent with internal dependency bumps recorded in the changelog. No further issues spotted.

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

3-3: Patch version increment acknowledged

1.8.5 → 1.8.6 aligns with workspace dependency updates. LGTM.

packages/remix/package.json (1)

3-3: Correct patch release

4.10.5 → 4.10.6 is consistent with the coordinated set of updates. Nothing else changed. ✅

packages/astro/package.json (1)

3-3: Astro SDK patch bump verified

2.10.9 → 2.10.10 matches internal dependency bumps; no additional adjustments required.

packages/themes/CHANGELOG.md (1)

3-9: Changelog entry added correctly

The new 2.4.1 section clearly documents the dependency bump to @clerk/[email protected]. Formatting remains consistent with previous entries.

packages/vue/package.json (1)

3-3: Version bump LGTM

The version in package.json matches the new changelog entry (1.8.20).

packages/react/package.json (1)

3-3: Version bump looks correct

5.35.45.35.5 follows semver for a patch-level change and keeps the package inside packages/ with the correct @clerk scope. No further issues spotted.

packages/localizations/CHANGELOG.md (1)

3-9: Changelog entry is minimal but sufficient

The entry clearly states this release is dependency-only (@clerk/[email protected]). Nothing else required.

packages/types/CHANGELOG.md (1)

3-11: Changelog entry looks solid.

The new 4.70.0 notes are clear, correctly linked, and follow the existing formatting conventions. No issues spotted.

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

7-13: Excellent, clear description of Billing Beta changes

The bullet points concisely explain the type rename, API deprecation, and hook replacement. No further action needed.

@panteliselef panteliselef reopened this Jul 24, 2025
@panteliselef panteliselef enabled auto-merge (squash) July 24, 2025 08:34
@panteliselef panteliselef merged commit 1af2504 into main Jul 24, 2025
63 of 64 checks passed
@panteliselef panteliselef deleted the changeset-release/main branch July 24, 2025 09:02
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