Repository navigation
chore: patch Wrangler tooling security dependencies - #27
Merged
Merged
Conversation
adewale
pushed a commit
that referenced
this pull request
Oct 10, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012eisRQmQvg4TphwztxhQGJ
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.
What
Patch the project's pinned development-only Wrangler from 4.137.0 to 4.149.0 and regenerate its npm lockfile.
Why
The auxiliary tooling audit in portfolio follow-up #32 found four high affected entries in Wrangler/Miniflare/Sharp/Undici. Full npm audit now reports zero.
Scope
Only package.json/package-lock.json. Python production locks (uv.lock and pylock.toml), Workers compatibility settings, content, generated assets, tests and CI are unchanged. No runtime dependency upgrade or paid provider calls.
Verification
249 existing Python unit tests pass with locked Python 3.13. The patched Wrangler reports 4.149.0 under the required Node 22 (an ephemeral local binary, not a system upgrade or project dependency). Full npm audit and whitespace check pass. Existing exact-head CI must prove the local Python Worker/browser gates and unchanged runtime lock before merge; local unit tests alone do not prove Pyodide integration.
Risk
A development/runtime-tool upgrade, not a production Python package update. No new job, mutation campaign, deploy or live-service smoke was run.