ci(repo): Version packages #6385
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📝 WalkthroughWalkthroughThis change updates the version numbers and changelogs for multiple packages to reflect the upgrade of the Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Complexity label: Trivial Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (50)
💤 Files with no reviewable changes (6)
✅ Files skipped from review due to trivial changes (13)
🚧 Files skipped from review as they are similar to previous changes (31)
⏰ 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)
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (10)
packages/testing/package.json (1)
3-3: Confirm new version is reflected in CHANGELOG
Please ensurepackages/testing/CHANGELOG.mdincludes an entry for v1.10.7 so downstream consumers can trace the update.packages/agent-toolkit/package.json (1)
3-3: Add matching CHANGELOG entry for v0.1.14
Keeping the changelog in sync with this patch bump will help users understand that the only change is the@clerk/backenddependency update.packages/fastify/package.json (1)
3-3: Document v2.4.13 in package changelog
A brief note that this release bumps@clerk/backendto 2.6.0 would complete the release metadata.packages/nuxt/package.json (1)
3-3: Update CHANGELOG for v1.7.14
Consider adding a line noting the dependency alignment with@clerk/backend2.6.0 to maintain clear release history.packages/express/package.json (1)
3-3: Ensure CHANGELOG mentions v1.7.13 patch
Recording this patch—including the backend bump—keeps the changelog accurate and aids consumers reviewing upgrade paths.packages/tanstack-react-start/CHANGELOG.md (1)
3-9: Changelog entry looks good – minor nitpick on context.Consider adding a short sentence explaining what the
@clerk/[email protected]change (Commerce webhook types) means for consumers of@clerk/tanstack-react-start, to make the changelog self-contained for package users who may not follow the upstream repo.packages/remix/CHANGELOG.md (1)
3-9: Add release date for parity with prior entriesPrevious sections often record the calendar date alongside the version header. Appending a date (
## 4.10.7 – 2025-07-xx) keeps the changelog uniformly searchable and time-ordered.packages/fastify/CHANGELOG.md (1)
3-9: Changelog entry looks good, but consider clarifying the impactThe patch entry correctly documents the dependency bump.
For consistency with earlier entries, add a short sentence on why the@clerk/backendupgrade matters (e.g., “adds types for Commerce webhooks”) so users don’t have to cross-reference other package logs.packages/nextjs/CHANGELOG.md (2)
3-9: Changelog entry looks good but could reference the companion changesetThe entry is concise and lists the dependency bump; however, providing the changeset filename (e.g.
.changeset/xxxx.md) or PR number (6385) next to the bullet would make provenance clearer for future readers.- ### Patch Changes - - Updated dependencies [...] + ### Patch Changes + - Updated dependencies (via PR #6385 / changeset `ci-version-packages-2bbeaf3`):
7-9: Consider listing transitive packages for quick scanningMany teams scan changelogs to see all packages indirectly affected. A short sub-list (in the same bullet) of key leaf packages upgraded by the bump (e.g.
@clerk/agent-toolkit,@clerk/express, …) would save a hop to other change logs.No action required if the team prefers minimal entries.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (23)
.changeset/lucky-papers-act.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/express/CHANGELOG.md(1 hunks)packages/express/package.json(1 hunks)packages/fastify/CHANGELOG.md(1 hunks)packages/fastify/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/remix/CHANGELOG.md(1 hunks)packages/remix/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)
💤 Files with no reviewable changes (1)
- .changeset/lucky-papers-act.md
🧰 Additional context used
📓 Path-based instructions (4)
**/*.{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/backend/package.jsonpackages/testing/package.jsonpackages/agent-toolkit/package.jsonpackages/fastify/package.jsonpackages/remix/package.jsonpackages/tanstack-react-start/package.jsonpackages/express/package.jsonpackages/agent-toolkit/CHANGELOG.mdpackages/react-router/package.jsonpackages/astro/package.jsonpackages/astro/CHANGELOG.mdpackages/nuxt/CHANGELOG.mdpackages/express/CHANGELOG.mdpackages/testing/CHANGELOG.mdpackages/tanstack-react-start/CHANGELOG.mdpackages/nextjs/package.jsonpackages/react-router/CHANGELOG.mdpackages/backend/CHANGELOG.mdpackages/remix/CHANGELOG.mdpackages/nuxt/package.jsonpackages/nextjs/CHANGELOG.mdpackages/fastify/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/backend/package.jsonpackages/testing/package.jsonpackages/agent-toolkit/package.jsonpackages/fastify/package.jsonpackages/remix/package.jsonpackages/tanstack-react-start/package.jsonpackages/express/package.jsonpackages/react-router/package.jsonpackages/astro/package.jsonpackages/nextjs/package.jsonpackages/nuxt/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/securityin 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/backend/package.jsonpackages/testing/package.jsonpackages/agent-toolkit/package.jsonpackages/fastify/package.jsonpackages/remix/package.jsonpackages/tanstack-react-start/package.jsonpackages/express/package.jsonpackages/agent-toolkit/CHANGELOG.mdpackages/react-router/package.jsonpackages/astro/package.jsonpackages/astro/CHANGELOG.mdpackages/nuxt/CHANGELOG.mdpackages/express/CHANGELOG.mdpackages/testing/CHANGELOG.mdpackages/tanstack-react-start/CHANGELOG.mdpackages/nextjs/package.jsonpackages/react-router/CHANGELOG.mdpackages/backend/CHANGELOG.mdpackages/remix/CHANGELOG.mdpackages/nuxt/package.jsonpackages/nextjs/CHANGELOG.mdpackages/fastify/CHANGELOG.md
packages/**/CHANGELOG.md
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Maintain detailed changelogs
Files:
packages/agent-toolkit/CHANGELOG.mdpackages/astro/CHANGELOG.mdpackages/nuxt/CHANGELOG.mdpackages/express/CHANGELOG.mdpackages/testing/CHANGELOG.mdpackages/tanstack-react-start/CHANGELOG.mdpackages/react-router/CHANGELOG.mdpackages/backend/CHANGELOG.mdpackages/remix/CHANGELOG.mdpackages/nextjs/CHANGELOG.mdpackages/fastify/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 (13)
packages/tanstack-react-start/package.json (1)
3-3: Patch version bump looks correct
0.21.2 → 0.21.3is an appropriate patch increment for a dependency-only update. No further action needed.packages/backend/package.json (1)
3-3: Minor version bump acknowledged
2.5.2 → 2.6.0reflects a new (non-breaking) feature—adding Commerce webhook types. ✔️packages/nuxt/CHANGELOG.md (1)
3-9: Changelog entry is clear and complete
The new1.7.14patch entry correctly references commit2bbeaf3and the updated backend dependency. 👍packages/remix/package.json (1)
3-3: Patch version bump confirmed
4.10.6 → 4.10.7appropriately signals the transitive backend update. Looks good.packages/react-router/package.json (1)
3-3: Patch version bump confirmed
1.8.6 → 1.8.7is suitable for a dependency refresh with no API change. All good.packages/astro/package.json (1)
3-3: Version bump looks correctPatch bump to
2.10.11follows semver for a dependency-only change.packages/astro/CHANGELOG.md (1)
3-9: Changelog entry is clear and completeNew section accurately records the dependency update and links to the commit.
packages/testing/CHANGELOG.md (1)
3-8: Changelog entry looks goodEntry follows existing structure (version heading, “Patch Changes” subsection, bullet with commit link and dependency bump). No further action required.
packages/agent-toolkit/CHANGELOG.md (1)
3-8: Changelog entry looks goodConsistent formatting and sufficient detail for the patch-level release; no issues spotted.
packages/nextjs/package.json (1)
3-3: Version bump aligns with patch-level dependency update – LGTM
Patch-incrementing to6.26.1cleanly reflects the indirect upgrade to@clerk/[email protected]. No additional metadata tweaks required.packages/express/CHANGELOG.md (1)
3-9: Changelog entry added correctly
The new1.7.13section properly documents the dependency bump and links the commit. Looks good.packages/backend/CHANGELOG.md (1)
3-8: Changelog entry is consistent and completeFormatting matches previous entries and correctly documents the minor change. No action needed.
packages/react-router/CHANGELOG.md (1)
3-9: Changelog entry looks goodThe new 1.8.7 section follows the existing formatting, includes a concise description, and references the correct commit hash. Nothing else to address.
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/elements
@clerk/clerk-expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/clerk-react
@clerk/react-router
@clerk/remix
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/themes
@clerk/types
@clerk/upgrade
@clerk/vue
commit: |
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
dc58338 to
25ef68c
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
packages/react/CHANGELOG.md (1)
3-19: Add release date header and follow existing changelog sectionsEvery previous version block carries only the version header, but many include a date or a “Patch/Minor Changes” breakdown.
For consistency and clarity, please:
- Add a release date (e.g.
## 5.37.0 – 2025-07-xx) or keep the existing style used across neighbouring entries.- If any dependency bumps accompany the feature, include a
### Patch Changessection like the rest of the file.This keeps the changelog machine-parsable and consistent with the repo’s historical format.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (31)
.changeset/lucky-papers-act.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/elements/CHANGELOG.md(1 hunks)packages/elements/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/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/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)
💤 Files with no reviewable changes (1)
- .changeset/lucky-papers-act.md
✅ Files skipped from review due to trivial changes (15)
- packages/chrome-extension/package.json
- packages/nuxt/package.json
- packages/astro/package.json
- packages/fastify/package.json
- packages/react/package.json
- packages/remix/package.json
- packages/expo/package.json
- packages/elements/package.json
- packages/agent-toolkit/CHANGELOG.md
- packages/backend/CHANGELOG.md
- packages/astro/CHANGELOG.md
- packages/react-router/package.json
- packages/chrome-extension/CHANGELOG.md
- packages/elements/CHANGELOG.md
- packages/expo/CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (14)
- packages/backend/package.json
- packages/testing/package.json
- packages/agent-toolkit/package.json
- packages/express/package.json
- packages/tanstack-react-start/package.json
- packages/nuxt/CHANGELOG.md
- packages/react-router/CHANGELOG.md
- packages/express/CHANGELOG.md
- packages/nextjs/package.json
- packages/testing/CHANGELOG.md
- packages/fastify/CHANGELOG.md
- packages/tanstack-react-start/CHANGELOG.md
- packages/nextjs/CHANGELOG.md
- packages/remix/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/react/CHANGELOG.md
packages/**/CHANGELOG.md
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Maintain detailed changelogs
Files:
packages/react/CHANGELOG.md
**/*
⚙️ CodeRabbit Configuration File
**/*: If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.Whenever reviewing a pull request, if there are any changes that could impact security, always tag
@clerk/securityin 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/react/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: semgrep-cloud-platform/scan
- GitHub Check: Analyze (javascript-typescript)
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
25ef68c to
ca967ed
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
ca967ed to
d88cf83
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
d88cf83 to
16c0942
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
16c0942 to
25134c7
Compare
clerk-cookie
added
types
clerk-js
react
localizations
expo
chrome-extension
themes
elements
vue
labels
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
Patch Changes
b0fdc9e]:@clerk/[email protected]
Minor Changes
Introduce
<TaskSelectOrganization />component. (#6376) by @LauraBeatrisIt allows you to eject the organization selection task flow from the default
SignInandSignUpcomponents and render it on custom URL paths usingtaskUrls.Usage example:
Patch Changes
Remove cache revalidation hooks from pending session handling. This fixes unmounting issues from
SignInandSignUpAIOs during after-auth flows. (#6389) by @LauraBeatrisUpdated dependencies [
b0fdc9e]:@clerk/[email protected]
Minor Changes
Expose commerce hooks and components under the experimental module. (#6383) by @panteliselef
Patch Changes
2bbeaf3,cfa7882,b0fdc9e]:@clerk/[email protected]
Minor Changes
Expose commerce hooks and components under the experimental module. (#6383) by @panteliselef
Patch Changes
b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,b0fdc9e]:@clerk/[email protected]
Patch Changes
b0fdc9e,6876563,cfa7882]:@clerk/[email protected]
Patch Changes
cfa7882,b0fdc9e]:@clerk/[email protected]
Patch Changes
b0fdc9e,6876563,cfa7882,b0fdc9e]:@clerk/[email protected]
Patch Changes
b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,b0fdc9e]:@clerk/[email protected]
Patch Changes
b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,cfa7882,b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,cfa7882,b0fdc9e]:@clerk/[email protected]
Patch Changes
b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,cfa7882,b0fdc9e]:@clerk/[email protected]
Patch Changes
2bbeaf3,b0fdc9e]:@clerk/[email protected]
Patch Changes
b0fdc9e]:@clerk/[email protected]
Patch Changes
<TaskSelectOrganization />component. (#6376) by @LauraBeatris@clerk/[email protected]
Patch Changes
b0fdc9e]:Summary by CodeRabbit
New Features
<TaskSelectOrganization />component, allowing custom organization selection flows.Bug Fixes
Chores