Repository navigation
chore(deps): override undici to patched versions (8.12.2 / 6.29.0) - #19
Merged
Merged
Conversation
TheStreamCode
added a commit
that referenced
this pull request
Nov 1, 2026
Follow-up to #19: replace the obscure {npm:{.:...}} override with plain {npm:12.2.1} and drop the ineffective nested undici rule (the copy is bundled inside the npm tarball, inBundle, so no override shape can move it). Resolved tree identical: undici 8.12.2 top-level, npm 12.2.1, nested undici 6.29.0. Co-authored-by: Michael Gasperini <michael@mikesoft.it>
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.
What
Pin the two locked
undicicopies to patched versions vianpm overrides(all dev-scope, transitive-only):node_modules/undici: 8.11.2 -> 8.12.2 (Dependabot first-patched for the 8.x advisories)node_modules/npm/node_modules/undici: 6.28.0 -> 6.29.0, by overriding the dev-transitivenpm12.2.0 -> 12.2.1 patch release. This copy ships bundled inside the npm tarball (inBundlein the lockfile), so anundiciversion selector cannot move it; 12.2.1 is the newest published npm and bundles undici 6.29.0.Lock diff is confined to the npm entry, its bundled composition, and top-level undici (12 entries, patch/minor only, no unrelated churn).
Alerts closed (expected on Dependabot rescan after merge)
8.x line -> 8.12.2 (5):
6.x line -> 6.29.0 (1):
Known remaining (blocked on an upstream npm release)
npm.undici: 6.29.1override is kept so it applies automatically if npm ever stops bundling; revisit thenpmpin when a release bundling undici >= 6.29.1 ships.Dev-scope rationale
Both undici copies are
"dev": truein package-lock.json and reachable only through theopenclawdevDependency (via openai, @openclaw/proxyline, and npm/node-gyp). The published package has no runtime dependency on undici. Thenpm12.2.0 -> 12.2.1 bump is a patch release of a dev-transitive tool whose only in-repo consumer isopenclaw(exact pin).Verification
npm cisucceeds and reproduces 8.12.2 / 6.29.0npm run typecheckandnpm run buildgreen;dist/unchanged after rebuildnpm test: 82/82 passed (7 files)Side note
The npm 12.2.1 bundle composition also moves bundled brace-expansion (5.0.12), ip-address (10.7.2), and postcss-selector-parser (7.1.6) past their alerted versions, so #18, #20, #12, #11, #36 may auto-close as well. No other copies of the alerted versions remain in the lock. Unrelated alerts (e.g. minimatch #46) are untouched.