ci: use npm ci with caching in all CI workflows#9150
Merged
ericpgreen2 merged 1 commit intomainfrom Apr 1, 2026
Merged
Conversation
Switch all GitHub Actions workflows from `npm install` to `npm ci` and enable npm caching via `actions/setup-node`. This hardens CI against supply chain attacks by ensuring only lockfile-pinned versions are installed, and speeds up installs by caching downloaded tarballs.
AdityaHegde
approved these changes
Mar 31, 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
2 participants
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.
Following the axios supply chain attack (PR #9148 pinned the affected package), this hardens all CI workflows against future npm supply chain attacks.
npm install→npm ciin all 6 workflows that install npm dependencies (includingscripts/web-test-code-quality.sh)cache: 'npm'to allactions/setup-node@v4stepsWhy
npm ci: Installs exactly frompackage-lock.json, never resolves new versions from the registry, and fails if the lockfile is out of sync withpackage.json. Even if a malicious version is published within a dependency's semver range, CI will only install what's in the committed lockfile.Why caching:
actions/setup-nodecaches~/.npm(npm's tarball cache) between runs, keyed by the lockfile hash. Packages are read from cache instead of re-downloaded from the registry. Typically cuts install time 50-70% on cache hits.Checklist:
Developed in collaboration with Claude Code