Repository navigation
fix(deps): allowlist npm-bundled undici for two new TLS advisories - #265
Merged
Merged
Conversation
GHSA-2m5v-pch6-74hx and GHSA-qrxm-fqhp-jwvm (both high, published 2026-10-27) fail the audit gate on every PR and on main. The lockfile's own undici copies (6.29.1, 7.30.1) are already patched by #262; the only affected copy is undici 6.29.0 bundled inside npm 11.21.1, which a lockfile update or override cannot change. npm/cli#10170 bumped the bundled undici to 6.29.1 and is merged, but it ships in npm 11.21.2, which is not published yet. Both advisories are allowlisted for that copy until 2026-11-15, alongside GHSA-xjj6, whose reason now points at the merged fix instead of the closed issue.
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 29, 2026
## [5.0.17](v5.0.16...v5.0.17) (2026-10-29) ### Bug Fixes * **deps:** allowlist npm-bundled undici for two new TLS advisories ([#265](#265)) ([543eeb5](543eeb5)), closes [#262](#262) [npm/cli#10170](npm/cli#10170) * **deps:** patch undici and zod advisories that turned the audit gate red ([#262](#262)) ([5484ce6](5484ce6)) * **site:** tighten the tempo readouts seen on the live pages ([c8558a3](c8558a3))
Contributor
|
🎉 This PR is included in version 5.0.17 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Why
Since 2026-10-27, two new high undici advisories fail "Audit dependencies" on every PR, and on main too (seen on #264, run 40939767311):
The lockfile's own undici copies are already patched: #262 moved them to 6.29.1 (
@actions/http-client) and 7.30.1 (@semantic-release/github). The only copy still affected is undici 6.29.0 bundled inside npm 11.21.1, which@semantic-release/npmpulls in. A bundled dependency can't be changed by a lockfile update or byoverrides, and 11.21.1 is the newest npm 11 published.What changes
bin/audit-gate.mjsonly, with no lockfile change.node_modules/npm/'s undici, until 2026-11-15. They are path-scoped, so a direct undici copy would still block.Once npm 11.21.2 is published, a targeted
npm update npmshould clear all three. The gate will then report the entries as stale, and they can be removed. If that hasn't happened, CI goes red again on 2026-11-16 and forces a re-check.Dev and release tooling only. The library ships no runtime dependencies, so none of this reaches consumers.
Evidence
Locally with npm 11.19.1 (CI's version):
Before this change, the same gate printed
BLOCKINGfor GHSA-2m5v and GHSA-qrxm.Unblocks #264 (the 5.1.0 release), which needs a rebase onto this.