Skip to content

fix(deps): raise the sharp override to the patched 0.35.4 - #206

Merged
catomean merged 1 commit into
mainfrom
chore/sharp-patched
Sep 25, 2026
Merged

catomean merged 1 commit into
mainfrom
chore/sharp-patched

Conversation

@catomean

Copy link
Copy Markdown
Collaborator

The last open advisory here is sharp < 0.35.4 (high). It wasn't a missing patch: next 16.3.5 already asks for ^0.35.4. The workspace override sharp: ^0.35.3 was holding the lockfile below the fix that next would have pulled in on its own. An override set below the advisory keeps the vulnerable version while looking handled.

The change raises it to ^0.35.4, which is the same minor, one patch up. The lockfile diff is sharp's per-platform packages being renamed.

Checked: 0 advisories left.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NLZ6vs1jsWw2kKbpWTZHf2

The last open advisory here was sharp < 0.35.4 (high). It was not an unpatched
dependency: next 16.3.5 already asks for ^0.35.4. The workspace override
`sharp: ^0.35.3` was holding the lockfile BELOW the fix next would have pulled
on its own -- an override floor under the advisory pins the vulnerable
version while reading as handled. Same minor, one patch up.

Verified: 0 advisories left.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NLZ6vs1jsWw2kKbpWTZHf2
@catomean
catomean merged commit cc3b08e into main Sep 25, 2026
1 check passed
@catomean
catomean deleted the chore/sharp-patched branch September 25, 2026 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant