fix(repo): Update lockfile with pnpm dedupe

[LauraBeatris]

Description

Fixes CI step

Checklist

• pnpm test runs as expected.
• pnpm build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Summary by CodeRabbit

• Chores
  • Internal changeset infrastructure update with no user-facing changes.

[changeset-bot]

🦋 Changeset detected

Latest commit: 733a371

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
clerk-js-sandbox	Ready	Preview	Comment	Nov 3, 2025 2:21pm

[coderabbitai]

Walkthrough

A new changeset file is added at .changeset/khaki-zoos-take.md containing only two YAML document separator lines and no substantive content or API changes.

Changes

Cohort / File(s)	Summary
Changeset entry \.changeset/khaki-zoos-take\.md	New file containing two YAML document separator lines (---) and no other content

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify filename and location in .changeset/
• Confirm whether the file is intentionally a placeholder or should be replaced with real changeset content

Poem

🐰 A tiny file hops in, neat and light,
Two dashed lines gleam in morning's sight,
No code to change, no bells to peal,
A quiet marker, soft and real.
✨

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'fix(repo): Update lockfile with pnpm dedupe' directly and clearly describes the main change in the changeset. The title accurately reflects that the PR updates the lockfile using pnpm dedupe, which aligns with the PR objectives of fixing a failing CI step. The title is concise, specific, and follows conventional commit formatting.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch laura/fix-ci-pnpm-dedupe-2

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 5b85ea9 and 733a371.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• .changeset/khaki-zoos-take.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

• .changeset/khaki-zoos-take.md

🪛 LanguageTool

.changeset/khaki-zoos-take.md

[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- ---

(QB_NEW_DE)

⏰ 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: Build Packages
• GitHub Check: Formatting | Dedupe | Changeset
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: semgrep-cloud-platform/scan
• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (1)

.changeset/khaki-zoos-take.md (1)

1-2: ****

The changeset file is valid. Empty changesets (containing only --- and ---) are intentionally used in Changesets for CI that requires a changeset file when there are no actual releases needed.

The git history shows the pnpm dedupe commit (a lockfile maintenance operation with no code changes) followed by pnpm changeset --empty, which is the correct approach. No package metadata or descriptions should be added since no packages were modified.

Likely an incorrect or invalid review comment.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/elements

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

@clerk/clerk-expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/clerk-react

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

@clerk/react-router

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

@clerk/remix

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/themes

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

@clerk/types

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

@clerk/upgrade

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

@clerk/vue

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

commit: 733a371

[blacksmith-sh]

Found 8 test failures on Blacksmith runners:

Test	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:110:9 › pricing table @billing › long-running--withBilling.astro. node › when signed in flow › subscribes to a plan	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:110:9 › pricing table @billing › long-running--withBilling.next.a ppRouter › when signed in flow › subscribes to a plan	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:110:9 › pricing table @billing › long-running--withBilling.vue.vi te › when signed in flow › subscribes to a plan	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:250:7 › pricing table @billing › long-running--withBilling.astro. node › starts free trial subscription for new user	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:250:7 › pricing table @billing › long-running--withBilling.next.a ppRouter › starts free trial subscription for new user	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:385:7 › pricing table @billing › long-running--withBilling.next.a ppRouter › subscribing to other paid plans while on free trial is immediate cancellatio n	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:456:9 › pricing table @billing › long-running--withBilling.vue.vi te › in UserProfile › renders pricing table, subscribes to a plan, revalidates payment method on complete and then downgrades to free	View Logs
[chrome] › integration/tests/ pricing-table.test.ts:588:9 › pricing table @billing › long-running--withBilling.next.a ppRouter › in UserProfile › adds payment method via checkout and resets stripe setup in tent after failed payment	View Logs