build(deps): refresh Worker tooling and fix sharp advisory - #25
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
1 participant
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.
Refresh the existing development toolchain: Cloudflare Workers types to 5.20260923.1, Vitest to 5.0.1, and Wrangler to 4.136.3. Regenerate the npm lockfile and match the allowed workerd install script to 1.20260921.1.
This pulls in sharp 0.35.4 through Miniflare and removes the three high-severity audit findings caused by GHSA-rgj7-g3m4-5g8c. Node 24, npm, the Worker compatibility date, and the deployed application contract remain unchanged. Checkout and setup-node already use their current v7 majors.
Validation: a remote Linux runner with Node 24.18.1 passed
npm ci && npm run check && npx wrangler deploy --dry-run && npm audit && npm outdated --json: vocabulary consistency, TypeScript, all 407 tests in 12 files (including workerd HTTP tests), Worker build, zero audit vulnerabilities, and no outdated direct dependencies. Independent Codex review found no actionable P0–P2 findings.