Caching npm deps in lint CI

[jamesbraza]

lint workflow got killed in this CI run by 403s:

Run suzuki-shunsuke/github-action-renovate-config-validator@v2.0.0
Run actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f
Found in cache @ /opt/hostedtoolcache/node/24.13.0/x64
(node:4098) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Environment details
Run set -eu
npm error code E403
npm error 403 403 Forbidden - GET https://registry.npmjs.org/to-regex-range
npm error 403 In most cases, you or one of your dependencies are requesting
npm error 403 a package version that is forbidden by your security policy, or
npm error 403 on a server you do not have access to.
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-02-25T18_45_05_471Z-debug-0.log

Let's add npm caching to speed this up and increase reliability

[dosubot]

Related Documentation

Checked 1 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[Copilot]

Pull request overview

This PR adds npm caching to the lint CI workflow to improve reliability and prevent 403 errors from npm registry rate limiting that were observed during the renovate-config-validator step.

Changes:

• Added actions/cache@v5 configuration for npm dependencies before the renovate-config-validator action
• Cache stores ~/.npm directory with a key based on the runner OS

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Consider adding a 'restore-keys' configuration to provide a fallback mechanism. This would allow the cache to be restored from a partial key match if an exact match isn't found, which is particularly useful during dependency updates.

The Docling cache implementation at lines 121-122 demonstrates this pattern:

key: ${{ runner.os }}-docling-${{ hashFiles('uv.lock') }}
restore-keys: ${{ runner.os }}-docling-

For this npm cache, you could add:

restore-keys: |
  renovate-npm-${{ runner.os }}-

This would allow the workflow to reuse a previous cache even if the key has changed, reducing the likelihood of hitting rate limits during cache misses.

Suggested change

	key: renovate-npm-${{ runner.os }}
	key: renovate-npm-${{ runner.os }}
	restore-keys: |
	renovate-npm-${{ runner.os }}-