fix(deps): clear all advisories — 3 to 0 - #3
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 54 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: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✨ 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 |
- next 15.2.8 -> 15.5.21, pinned exactly as this repo already pinned it; carries the patched sharp - postcss direct devDependency -> ^8.5.10, XSS via unescaped </style> in stringify output, GHSA-qx2v-qp2m-jg93 - sharp ^0.35.3 via overrides, libvips CVEs GHSA-f88m-g3jw-g9cj - brace-expansion pinned per major range postcss had to be raised as a direct dependency rather than overridden: npm rejects an override conflicting with a declared direct dependency (EOVERRIDE). brace-expansion is pinned per major (<2 -> ^1.1.16, 2.x -> ^2.1.2, >=3 -> >=5.0.7) rather than flat. Its advisories span three disjoint ranges, and a flat >=5.0.7 forces 5.x onto minimatch@3, which relies on the CJS `expand` export that 5.x dropped. An earlier revision of this branch used `^15.5.21` and a flat brace-expansion override, and Vercel failed the preview deploy while lint and build both passed in CI and locally under `npm ci` and `npm install`. The build log was not accessible, so rather than guess, the diff was reduced to the minimum that still clears every advisory: exact pin restored, override narrowed. Verified: npm audit 0 vulnerabilities, eslint clean, next build succeeds.
1 participant
in stringify output, GHSA-qx2v-qp2m-jg93
postcss had to be bumped as a direct dependency rather than overridden: npm
rejects an override that conflicts with a declared direct dependency
(EOVERRIDE).
Verified: npm audit reports 0 vulnerabilities.