Repository navigation
chore: force patched fast-uri, svgo, sharp via pnpm overrides - #353
Conversation
pnpm audit --audit-level=high went red on main (last green 189135a) when four high advisories were published against existing transitive deps: - fast-uri >=3.0.0 <3.1.4 — two host-confusion advisories incl. GHSA-v2hh-gcrm-f6hx (via ajv across commitlint/webpack/storybook). 3.1.4 was published 2026-07-19, inside the 3-day cooldown, so fast-uri is also added to minimumReleaseAgeExclude (the documented urgent-patch path); the exclusion can be dropped after 2026-07-22. - svgo >=3.0.0 <3.3.4 — removeScripts leaves executable content (via Docusaurus image tooling). - sharp <0.35.0 — inherited libvips CVEs (via wrangler>miniflare, CI-only deploy tooling whose native build is already blocked in allowBuilds). Same mechanism as the serialize-javascript and brace-expansion precedents. Remaining findings are 1 low + 3 moderate, below the CI gate.
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ 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 |
Preview DeploymentPreview URL: https://148bf69b.bestax.pages.dev |
|
🎉 This PR is included in version 5.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 3.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 participant
Summary
pnpm audit --audit-level=highwent red on main yesterday (first failing run:4b58739; last green:189135a) when four high advisories were published against existing transitive deps — this is currently failing every open PR's CI (#347, #352, …). Nothing in the tree changed; the advisories are new.Fix follows the repo's existing override precedents (serialize-javascript, brace-expansion):
fast-uri>=3.1.4 <4svgo>=3.3.4 <4sharpallowBuilds)>=0.35.0fast-uri@3.1.4was published 2026-07-19, inside the 3-dayminimumReleaseAgecooldown, so it's also added tominimumReleaseAgeExclude— the path the file itself documents for urgent patches. The exclusion is safe to drop after 2026-07-22 (noted in the comment).Verification
pnpm installre-resolved cleanly (+7/−7 packages), lockfile passes the supply-chain policy check.pnpm audit --audit-level=highnow exits 0 — remaining findings are 1 low + 3 moderate, below the CI gate.After this merges, the other open PRs need a rebase or a CI re-run to go green.