build(deps-dev): bump undici past security advisory - #43
Merged
Conversation
Refreshes the lockfile so all three transitive undici copies clear the advisory ranges (< 6.27.0, >= 7.0.0 < 7.28.0): undici 7.24.4 -> 7.29.0 @actions/http-client/../undici 6.24.1 -> 6.28.0 npm/node_modules/undici (bundled) 6.25.0 -> 6.27.0 (npm 11.14.1 -> 11.19.0) Dependabot could not do this on its own: the third copy is bundled inside the npm tarball, so bumping it required moving npm itself, which was out of scope for a job pinned to `dependencies: ["undici"]` with `update-subdependencies: false`. The run failed with security_update_not_possible (latest-resolvable 6.25.0, lowest-non- vulnerable 6.27.0). All three copies are dev-only and never ship in the published bundle. No package.json change needed — the existing `npm` override already permits 11.19.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vh-fsantos
approved these changes
Aug 3, 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
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.
Fixes the failing Dependabot security update for
undici(run 30823213256).Why Dependabot couldn't do this itself
The job failed with:
undiciisn't a direct dependency — there are three transitive copies, all undersemantic-release. Two of them were freely bumpable, but the third lives atnode_modules/npm/node_modules/undiciwithinBundle: true, i.e. vendored inside thenpm@11.14.1tarball. Dependabot can't rewrite a bundled dependency in place; the only way to move it is to bumpnpmitself, which was out of scope for a job pinned todependencies: ["undici"]withupdate-subdependencies: falseandallowed-updates: direct. So it had no path forward and errored instead of opening a PR.What this does
A lockfile refresh (
npm update undici npm --package-lock-only) moves all three copies past the advisory:undici@actions/http-client/…/undicinpm/node_modules/undici(bundled)All clear the advisory ranges
< 6.27.0and>= 7.0.0 < 7.28.0.No
package.jsonchange is required — the existing"npm": ">=11.14.1 <12.0.0"override already permits 11.19.0.Scope and risk
npmbundled tree plus the two standaloneundicicopies. No production dependencies touched.dev: true;undicinever ships in the published browser bundle, so real-world exposure was nil — this was CI noise rather than a shipped vulnerability.build(deps-dev):rather thanfix:so semantic-release doesn't cut a release for a dev-only lockfile change.Verification
npm install— clean, no lockfile driftnpm run build(tsc && esbuild) — passes,static/cdn.js5.3kbundiciversions fall outside every advisory range in the job definition🤖 Generated with Claude Code