chore: upgrade pnpm to 11.8.0 and resolve audit vulnerabilities#466
Conversation
- Bump packageManager to pnpm@11.8.0 (with verified integrity hash) - Move pnpm overrides from package.json to pnpm-workspace.yaml - Fix 3 advisories surfaced by `pnpm audit`: - vite 6.4.2 -> 6.4.3 (GHSA-fx2h-pf6j-xcff high, GHSA-v6wh-96g9-6wx3) - postcss override ^8.5.10 (GHSA-qx2v-qp2m-jg93) pnpm audit now reports no known vulnerabilities; build passes.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 56 minutes and 9 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughUpgrades pnpm from v10 to v11.8.0 by updating the Changespnpm v11 Upgrade
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
…link - AGENTS.md: open PRs against `master` (was `preview`) - AGENTS.md: package manager note pnpm 10 -> 11.8.0 - Add CLAUDE.md -> AGENTS.md symlink so Claude Code loads the conventions
Summary
packageManagerinpackage.json, with verified integrity hash)overridesout ofpackage.jsonintopnpm-workspace.yaml(the location pnpm now expects)pnpm audit/ DependabotAGENTS.md, add aCLAUDE.mdsymlinkVulnerabilities fixed
server.fs.denybypass on Windows</style>The existing override was pinning
viteto the vulnerable6.4.2, so both vite advisories traced back to it. Bumped to6.4.3(latest in the 6.x line) to stay compatible with vitepress 1.6.x and@tailwindcss/viterather than jumping to 7.x.postcssis transitive, so an override forces the patched line.Docs / tooling
AGENTS.md: open PRs againstmaster(previously documentedpreview); package-manager notepnpm 10→pnpm 11.8.0.CLAUDE.md→AGENTS.mdsymlink so Claude Code loads the repo conventions automatically.Verification
pnpm audit→ No known vulnerabilities foundpnpm build→ completes successfully (builds bundles, renders pages, generates sitemap)Summary by CodeRabbit
Chores
Documentation