fix(repo): override sharp to >=0.35.0 to clear libvips advisory#2548
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe root Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8)package.jsonTraceback (most recent call last): pnpm-workspace.yamlTraceback (most recent call last): 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. 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 |
mandarini
marked this pull request as ready for review
July 22, 2026 13:57
@supabase/auth-js
@supabase/functions-js
@supabase/postgrest-js
@supabase/realtime-js
@supabase/storage-js
@supabase/supabase-js
commit: |
Contributor
|
The following capabilities are marked
These may have been renamed, removed, or never registered. Please update the capability matrix. |
spydon
previously approved these changes
Jul 22, 2026
|
Coverage is 80.658% — fix/override-sharp-version into master. No base build found for |
|
Coverage is 80.658% — fix/override-sharp-version into master. No base build found for |
spydon
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
pnpm audit --audit-level=high --prodstep in CI started failing on every PR after the GHSA-f88m-g3jw-g9cj advisory (CVE-2026-33327 and related libvips issues) was published on 2026-07-21, flaggingsharp<0.35.0pulled transitively throughnextin the realtime-js example app. This adds asharp: >=0.35.0override inpnpm-workspace.yaml(the location this workspace reads overrides from in pnpm v11) sosharpresolves to a patched version and the audit gate passes again.Regenerating the lockfile bumps
sharpto 0.35.3 and, as a side effect of the full re-resolution, picks up a few age-eligible patch bumps in dev tooling and the example app (next16.2.9 to 16.2.10,@emnapi/runtime, and related wasm runtime bindings). None of these touch published package runtime code. After the change,pnpm audit --audit-level=high --prodreports no high-severity vulnerabilities.