chore(deps): pin bundled npm to 12.1.0 - #54
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pins the globally installed npm in the runtime image to 12.1.0, replacing the
floating
npm@12.npm ships its dependency tree bundled inside its own tarball, so those versions
are pinned by npm's lockfile rather than by anything in this Dockerfile. The
current
latestimage resolvednpm@12to 12.0.2, which bundlesundici@6.27.0; 12.1.0 bundlesundici@6.28.0, carrying the fixes forCVE-2026-16728, CVE-2026-15157 and CVE-2026-16729.
Pinning the exact version also makes the bundled dependency set reproducible
instead of varying with build date.
http-cache-semantics@4.2.0is bundled unchanged in every npm release including12.1.0, and 4.2.0 is the latest published version, so CVE-2026-93748 and
CVE-2026-93750 are unaffected by this bump and are handled separately.