chore(deps-dev): bump worker dev dependencies past the sharp advisory - #60
Merged
Merged
Conversation
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
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.
This PR bumps the worker's dev dependencies to current and pins
sharpto a fixed release, clearing every advisory thatnpm audit --audit-level=lowreports.npm audithad gone red repo-wide on advisories published since the last run ofci.ymlonmain. Bumpingvitestto 4.1.11 clears the two moderate@vitest/mockerpath-traversal findings. The four high findings are the libheif vulnerabilities insharpbelow 0.35.4, reached throughminiflare. A top-levelwranglerat 4.136.1 resolvesminiflare5.20260921.0-alpha andsharp0.35.4 on its own, but@cloudflare/vitest-pool-workers0.22.0, the newest release, hard-pinswrangler4.124.0 andminiflare5.20260815.0-alpha, which carrysharp0.35.2. No published version of the pool package resolves that, so theoverridesentry forces the fixedsharpinto its subtree as well. The override can go once Cloudflare ships a pool release built on a currentminiflare.worker-configuration.d.tsis regenerated, sincewrangler typesoutput moves with thewranglerversion and CI asserts the committed file matches.This supersedes the four open Dependabot bumps, #43, #45, #57 and #58; #57 in particular stops short at
wrangler4.127.1, inside the advisory's 4.16.0 to 4.130.0 range.🤖 Prepared with Claude Code