What the numbers show
install ≥ 60s or ≥ 15% of the jobPackage managers re-download and re-link everything when nothing is cached. Cache the package manager's store, install from the lockfile only, and skip what the job doesn't need, such as browsers a unit job never opens.
The change
Turn on the setup action's built-in cache
- uses: actions/setup-node@v4 with: node-version: 22 cache: npm- run: npm ci --prefer-offline --no-auditVerify the verdict stays the same
- 01The lockfile is unchanged by the job.
- 02The second run's install step logs a cache hit.
- 03The job's conclusion matches on the same commit.