ci(repo): Version packages #6429
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@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: |
📝 WalkthroughWalkthroughThis change updates the patch versions and changelogs for multiple packages across the repository, primarily to reflect dependency updates. The dependency bumps focus on internal packages such as Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (60)
💤 Files with no reviewable changes (16)
✅ Files skipped from review due to trivial changes (17)
🚧 Files skipped from review as they are similar to previous changes (27)
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 (17)
packages/localizations/package.json (1)
3-3: Consistent patch bump; ensure changelog entry existsThe move to 3.20.6 keeps parity with the upstream @clerk/types patch. Double-check that
packages/localizations/CHANGELOG.mdincludes a note for 3.20.6 if it hasn’t already been updated.packages/nextjs/package.json (1)
3-3: Add corresponding CHANGELOG entry for 6.28.1The patch bump itself is fine, but make sure
packages/nextjs/CHANGELOG.md(or the repo-level changelog) records the new version and the dependency bumps for traceability.packages/fastify/package.json (1)
3-3: Don’t forget the 2.4.15 release notePlease add a short note in the Fastify package changelog so consumers know this is a dependency-only patch.
packages/tanstack-react-start/package.json (1)
3-3: Include 0.21.5 in changelogA matching changelog entry will keep version history coherent across the mono-repo.
packages/remix/package.json (1)
3-3: Document the 4.10.9 patchAdd a changelog snippet summarising the internal dependency bumps to maintain release transparency.
packages/testing/package.json (1)
3-3: Patch 1.10.9 needs a changelog linePlease append an entry for 1.10.9 indicating this is an internal dependency update only.
packages/vue/CHANGELOG.md (1)
3-10: Changelog entry looks complete – consider a one-liner for contextPatch version and dependency bumps are recorded correctly.
If space permits, adding a short note (e.g. “No runtime changes – internal deps only”) after the header can help downstream consumers scanning the log.packages/shared/CHANGELOG.md (1)
3-9: Add a release date for the new 3.16.1 entryAll previous versions in this file include only a header without a date, but adding the date right after the version header is customary and improves traceability when scanning the log. Consider appending the release date, e.g.:
-## 3.16.1 +## 3.16.1 – 2025-07-?? <!-- adjust accordingly -->packages/tanstack-react-start/CHANGELOG.md (1)
3-12: Consider adding a short rationale for the patch bumpPrevious entries often include a terse sentence explaining why the dependencies were bumped (e.g. a bug-fix, refactor, etc.).
Adding one here – e.g. “Align with billing statement / payment attempt loader refactor” – keeps the changelog self-contained and searchable.packages/backend/CHANGELOG.md (1)
3-10: Add release date to the new 2.6.2 entry for consistencyAll previous entries include the date in the heading (
## <version> – YYYY-MM-DD).
Adding the date here keeps the file machine-parsable and avoids merge conflicts when several releases land close together.-## 2.6.2 +## 2.6.2 – 2025-07-?? <!-- please fill in the actual release date -->packages/elements/CHANGELOG.md (1)
3-10: Consider adding a one-liner on the motivation for the bumpThe new 0.23.48 entry only lists dependency versions. A brief note (e.g. “Keeps Elements in sync with the billing-statement data-loader refactor shipped in @clerk/types 4.71.1”) would help future readers understand why the patch was published, matching the “detailed changelogs” guideline.
packages/express/CHANGELOG.md (1)
3-11: Consider adding a release date for consistency & traceability
Earlier entries don’t include dates, but adding a date (e.g. “2025-07-11”) right after the version header can help consumers quickly see when the patch went out.-## 1.7.15 +## 1.7.15 — 2025-07-11packages/react-router/CHANGELOG.md (1)
3-12: Changelog entry looks good – consider adding a one-line rationaleThe section is syntactically correct and follows the existing formatting.
If there is any user-visible behaviour change (even indirectly via the updated internals), a short note such as “No functional changes – internal deps only” helps consumers scanning the log.packages/clerk-js/CHANGELOG.md (1)
3-13: Add release date & keep entry metadata consistentAll recent Clerk changelog entries include the release date in the heading and, where relevant, a brief “Published” note. 5.78.1 is missing that metadata, which breaks the visual rhythm and makes automated date parsing harder.
Suggested tweak:
-## 5.78.1 +## 5.78.1 (2025-07-XX)(Replace the placeholder with the actual UTC date you cut the release.)
No content changes required—just the heading.
packages/chrome-extension/CHANGELOG.md (2)
3-10: Add a release date to keep the log chronologically searchableAll previous entries include only the version header, but many teams prefer appending the release date (e.g. “## 2.5.15 – 2024-07-09”) for quicker auditing.
Consider adding the date to preserve consistency with other first-party packages that do include it.
7-10: Avoid redundant wording in bullet listThe bullet list already appears under “Patch Changes”, yet each item starts with “Updated dependencies”.
Trimming the repeated phrase improves readability:- - Updated dependencies [...] + - [...]packages/expo/CHANGELOG.md (1)
3-12: Add release date for new version headerAll previous entries use the same “## ” format, so this is consistent.
However, consider appending the release date (e.g. “## 2.14.14 – 2025-07-xx”) to help readers quickly locate when a given patch shipped.
No functional change required—purely a docs nit.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (45)
.changeset/slow-foxes-lay.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/slow-foxes-lay.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/fastify/package.jsonpackages/expo-passkeys/package.jsonpackages/vue/package.jsonpackages/react/package.jsonpackages/astro/package.jsonpackages/elements/package.jsonpackages/localizations/package.jsonpackages/agent-toolkit/package.jsonpackages/backend/package.jsonpackages/nuxt/package.jsonpackages/themes/package.jsonpackages/expo/package.jsonpackages/react-router/package.jsonpackages/chrome-extension/package.jsonpackages/tanstack-react-start/package.jsonpackages/nextjs/package.jsonpackages/testing/package.jsonpackages/remix/package.jsonpackages/clerk-js/package.jsonpackages/vue/CHANGELOG.mdpackages/expo-passkeys/CHANGELOG.mdpackages/shared/package.jsonpackages/agent-toolkit/CHANGELOG.mdpackages/nuxt/CHANGELOG.mdpackages/testing/CHANGELOG.mdpackages/types/CHANGELOG.mdpackages/fastify/CHANGELOG.mdpackages/react-router/CHANGELOG.mdpackages/types/package.jsonpackages/shared/CHANGELOG.mdpackages/express/package.jsonpackages/themes/CHANGELOG.mdpackages/localizations/CHANGELOG.mdpackages/tanstack-react-start/CHANGELOG.mdpackages/express/CHANGELOG.mdpackages/nextjs/CHANGELOG.mdpackages/elements/CHANGELOG.mdpackages/backend/CHANGELOG.mdpackages/chrome-extension/CHANGELOG.mdpackages/astro/CHANGELOG.mdpackages/expo/CHANGELOG.mdpackages/react/CHANGELOG.mdpackages/clerk-js/CHANGELOG.mdpackages/remix/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/fastify/package.jsonpackages/expo-passkeys/package.jsonpackages/vue/package.jsonpackages/react/package.jsonpackages/astro/package.jsonpackages/elements/package.jsonpackages/localizations/package.jsonpackages/agent-toolkit/package.jsonpackages/backend/package.jsonpackages/nuxt/package.jsonpackages/themes/package.jsonpackages/expo/package.jsonpackages/react-router/package.jsonpackages/chrome-extension/package.jsonpackages/tanstack-react-start/package.jsonpackages/nextjs/package.jsonpackages/testing/package.jsonpackages/remix/package.jsonpackages/clerk-js/package.jsonpackages/shared/package.jsonpackages/types/package.jsonpackages/express/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/fastify/package.jsonpackages/expo-passkeys/package.jsonpackages/vue/package.jsonpackages/react/package.jsonpackages/astro/package.jsonpackages/elements/package.jsonpackages/localizations/package.jsonpackages/agent-toolkit/package.jsonpackages/backend/package.jsonpackages/nuxt/package.jsonpackages/themes/package.jsonpackages/expo/package.jsonpackages/react-router/package.jsonpackages/chrome-extension/package.jsonpackages/tanstack-react-start/package.jsonpackages/nextjs/package.jsonpackages/testing/package.jsonpackages/remix/package.jsonpackages/clerk-js/package.jsonpackages/vue/CHANGELOG.mdpackages/expo-passkeys/CHANGELOG.mdpackages/shared/package.jsonpackages/agent-toolkit/CHANGELOG.mdpackages/nuxt/CHANGELOG.mdpackages/testing/CHANGELOG.mdpackages/types/CHANGELOG.mdpackages/fastify/CHANGELOG.mdpackages/react-router/CHANGELOG.mdpackages/types/package.jsonpackages/shared/CHANGELOG.mdpackages/express/package.jsonpackages/themes/CHANGELOG.mdpackages/localizations/CHANGELOG.mdpackages/tanstack-react-start/CHANGELOG.mdpackages/express/CHANGELOG.mdpackages/nextjs/CHANGELOG.mdpackages/elements/CHANGELOG.mdpackages/backend/CHANGELOG.mdpackages/chrome-extension/CHANGELOG.mdpackages/astro/CHANGELOG.mdpackages/expo/CHANGELOG.mdpackages/react/CHANGELOG.mdpackages/clerk-js/CHANGELOG.mdpackages/remix/CHANGELOG.md
packages/localizations/**/*
📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)
Localization files must be placed in 'packages/localizations/'.
Files:
packages/localizations/package.jsonpackages/localizations/CHANGELOG.md
packages/**/CHANGELOG.md
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Maintain detailed changelogs
Files:
packages/vue/CHANGELOG.mdpackages/expo-passkeys/CHANGELOG.mdpackages/agent-toolkit/CHANGELOG.mdpackages/nuxt/CHANGELOG.mdpackages/testing/CHANGELOG.mdpackages/types/CHANGELOG.mdpackages/fastify/CHANGELOG.mdpackages/react-router/CHANGELOG.mdpackages/shared/CHANGELOG.mdpackages/themes/CHANGELOG.mdpackages/localizations/CHANGELOG.mdpackages/tanstack-react-start/CHANGELOG.mdpackages/express/CHANGELOG.mdpackages/nextjs/CHANGELOG.mdpackages/elements/CHANGELOG.mdpackages/backend/CHANGELOG.mdpackages/chrome-extension/CHANGELOG.mdpackages/astro/CHANGELOG.mdpackages/expo/CHANGELOG.mdpackages/react/CHANGELOG.mdpackages/clerk-js/CHANGELOG.mdpackages/remix/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). (4)
- GitHub Check: semgrep-cloud-platform/scan
- GitHub Check: Build Packages
- GitHub Check: semgrep/ci
- GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (28)
packages/types/package.json (1)
3-3: Patch bump looks correct and follows semverThe version is incremented from 4.71.0 → 4.71.1, which is appropriate for a patch-level change with no public-API surface modifications. No further action needed.
packages/shared/package.json (1)
3-3: Patch version 3.16.1 aligns with dependency updateThe internal utilities package stays in sync with the new @clerk/types version. LGTM.
packages/react/package.json (1)
3-3: Patch increment to 5.38.1 is appropriateNo breaking changes are implied; dependency constraints remain on workspace ranges. Good to ship.
packages/themes/package.json (1)
3-3: Patch bump to 2.4.4 acknowledgedMatches the coordinated release; nothing else changed. ✅
packages/chrome-extension/package.json (1)
3-3: Patch bump follows semver – looks good
No other metadata changes detected.packages/expo/package.json (1)
3-3: Version increment to 2.14.14 is appropriate
Consistent patch release across the workspace; no issues spotted.packages/elements/package.json (1)
3-3: Patch version 0.23.48 LGTM
Maintains semver integrity; workspace dependency ranges unchanged.packages/express/package.json (1)
3-3: 1.7.15 patch bump confirmed
Aligned with dependency updates; nothing further required.packages/expo-passkeys/package.json (1)
3-3: 0.3.25 patch bump looks correct
No additional modifications detected.packages/nuxt/package.json (1)
3-3: Patch bump correctly follows semver – LGTM
No additional issues spotted for this package.json.packages/clerk-js/package.json (1)
3-3: Version increment looks good
Patch release aligns with coordinated internal-dependency bumps. Nothing else to flag.packages/astro/package.json (1)
3-3: Semver patch bump verified
Change is minimal and consistent with repo-wide release process.packages/vue/package.json (1)
3-3: Patch version bump accepted
No semantic or formatting concerns.packages/agent-toolkit/package.json (1)
3-3: Agent-toolkit patch bump OK
Change is straightforward; no action required.packages/expo-passkeys/CHANGELOG.md (1)
3-10: Good dependency-bump entryNothing to add – version tag and updated-dependency block follow the repo’s changelog style.
packages/themes/CHANGELOG.md (1)
3-9: Changelog entry looks correct and follows the existing formatPatch version bump matches the dependency update and the commit link is present. No issues spotted.
packages/react-router/package.json (1)
3-3: Add a matching CHANGELOG entry for 1.8.9The version is bumped but the corresponding
packages/react-router/CHANGELOG.mdsnippet isn’t part of this diff. Double-check that a changeset generated a changelog section for1.8.9; if not, please add one to keep release history consistent.packages/backend/package.json (1)
3-3: Ensure changelog is updated for 2.6.2Same note as for
react-router: confirm thatpackages/backend/CHANGELOG.mdcontains a2.6.2entry produced by the changeset, otherwise the release notes will miss this patch.packages/agent-toolkit/CHANGELOG.md (1)
3-11: Changelog entry looks goodPatch bump and dependency list are clear and conform to the file’s style.
packages/nuxt/CHANGELOG.md (1)
3-11: Changelog formatting and content look goodEntry follows the existing style and correctly lists bumped internal dependencies.
No further action needed.packages/astro/CHANGELOG.md (1)
3-11: Changelog entry looks goodThe new
2.10.13patch section is correctly formatted and consistent with prior entries (heading levels, bullet list, commit link, dependency list).
No further action needed.packages/fastify/CHANGELOG.md (1)
3-11: Changelog entry looks correct & consistentThe new 2.4.15 patch entry follows the existing style, links to the commit, and lists the bumped internal dependencies with pinned versions. No further action needed.
packages/remix/CHANGELOG.md (1)
3-11: Changelog entry format looks good – no action requiredThe new
## 4.10.9section follows the existing formatting conventions (header, “Patch Changes” subsection, dependency list with commit link). No inconsistencies detected.packages/localizations/CHANGELOG.md (1)
3-11: Changelog entry looks correct and consistentVersion header, section structure, and dependency notes match the existing style. No issues found.
packages/react/CHANGELOG.md (1)
3-10: Changelog entry format is consistent – no issues foundThe new
## 5.38.1section follows the existing style (heading level, “Patch Changes” subsection, bullet list with dependency bumps). No action needed.packages/testing/CHANGELOG.md (1)
3-11: Changelog entry is clear and completeVersion heading, semantic version bump, and dependency list all follow the repository’s changelog conventions and accurately reflect the coordinated patch release. No action needed.
packages/types/CHANGELOG.md (1)
3-8: Changelog entry is consistent and well-formedThe heading, blank-line spacing, and bullet formatting align with the existing conventions in this file. No issues spotted.
packages/nextjs/CHANGELOG.md (1)
3-11: Changelog entry reads well and matches repository conventionsHeader, section titles, commit link, and dependency list are formatted consistently with prior entries. No issues observed.
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
0f6ad0a to
bd3ca05
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
bd3ca05 to
e8dec68
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
e8dec68 to
ffa0a14
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
ffa0a14 to
5933be4
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
5933be4 to
02c4564
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
02c4564 to
fea7568
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
fea7568 to
eaabe1a
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
eaabe1a to
c318e25
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
c318e25 to
35c68f6
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
35c68f6 to
0b2a0a2
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
0b2a0a2 to
a16ff80
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
a16ff80 to
22a7a1e
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
22a7a1e to
5a87538
Compare
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]: Update prefix for checkout status (#6438) by @panteliselef
Replaces
awaiting_withneeds_.[Billing Beta] Remove
statement_idfrom the checkout resource. (#6437) by @panteliselefPatch Changes
Add
inputmode="email"to email fields to help prompt mobile devices to use a virtual keyboard optimized for entering email addresses. (#6440) by @alexcarpenterFix TelemetryCollector logic for clerk-js in browser to properly populate sdkMetadata for telemetry events. (#6448) by @panteliselef
Display alert on plan details error (#6384) by @panteliselef
Added proper type checking before using the in operator to prevent errors when modal state contains non-object values (#6433) by @jacekradko
Refactor billing statement page and payment attempt page data loading (#6420) by @aeliox
Added temporary patch for API keys pagination compatibility (#6451) by @wobsoriano
Fix SSO callback for after-auth custom flows (#6430) by @LauraBeatris
Updated dependencies [
7a46679,05cc5ec,22c35ef,c69de58,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Minor Changes
statement_idfrom the checkout resource. (#6437) by @panteliselefPatch Changes
Fixes a bug which cause initialization of a payment method to never fire. (#6436) by @panteliselef
Fix TelemetryCollector logic for clerk-js in browser to properly populate sdkMetadata for telemetry events. (#6448) by @panteliselef
Remove
treatPendingAsSignedOutfromuseSessionand always return pending session (#6432) by @LauraBeatrisUpdated dependencies [
22c35ef,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Minor Changes
[Billing Beta]: Update prefix for checkout status (#6438) by @panteliselef
Replaces
awaiting_withneeds_.[Billing Beta] Remove
statement_idfrom the checkout resource. (#6437) by @panteliselefPatch Changes
Fix
UseSessionReturn['session']JSDocs to not mention active status, since pending sessions are also returned (#6430) by @LauraBeatrisRemove
treatPendingAsSignedOutfromuseSessionand always return pending session (#6432) by @LauraBeatrisRefactor billing statement page and payment attempt page data loading (#6420) by @aeliox
@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
Fix
async_hooksimport for better Cloudflare compatibility. (#6287) by @mlafeldtUpdated dependencies [
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
Fix Node 18 compatibility issues with
snakecase-keys. (#6441) by @wobsorianoUpdated dependencies [
7a46679,05cc5ec,22c35ef,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
123c578,7a46679,05cc5ec,813e738,22c35ef,aa9f185,6cb2277,af0e123,241bbbd,811019d,3d1d871,e8d816a]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,e8d816a,aa9f185,af0e123,241bbbd,3d1d871]:@clerk/[email protected]
Patch Changes
123c578,7a46679,05cc5ec,813e738,22c35ef,e8d816a,aa9f185,6cb2277,af0e123,241bbbd,811019d,3d1d871,e8d816a]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
Add ja-JP translations in
<UserProfile/>. (#6426) by @tsume-haRefactor billing statement page and payment attempt page data loading (#6420) by @aeliox
Updated dependencies [
22c35ef,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
Fixes a bug which cause initialization of a payment method to never fire. (#6436) by @panteliselef
Updated dependencies [
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,241bbbd,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
Fixes a bug which cause initialization of a payment method to never fire. (#6436) by @panteliselef
Resolve dynamic menu items losing icons (#6443) by @wobsoriano
Updated dependencies [
7a46679,05cc5ec,22c35ef,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,241bbbd,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,241bbbd,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,241bbbd,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,8c7e5bb,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
Add
shadcn.cssexport for importing within stylesheets to resolve Tailwind not picking up the elements class names used within the shadcn theme. (#6415) by @alexcarpenterUpdated dependencies [
22c35ef,e8d816a,aa9f185,af0e123,3d1d871]:@clerk/[email protected]
Patch Changes
7a46679,05cc5ec,22c35ef,e8d816a,aa9f185,af0e123,3d1d871]:Summary by CodeRabbit
Bug Fixes
Enhancements
Localization
Dependency Updates
Chores