You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Lockfile verification cache never restores when devEngines warns about the Node version #73
With devEngines.runtime.onFail: "warn" in package.json, the lockfile verification cache is never restored or saved. Nothing in the log says why. Every job prints Lockfile verification cache is not found, even when an entry with that exact key is in the repo's Actions cache, and no job saves a new one. In our repo, verifying went from cached to 8.3 s per job.
Cause
The action restores the verification cache before it installs the project's runtime, so pnpm cache path runs under the runner's Node. pnpm then prints its devEngines warning on stdout, before the path (pnpm/pnpm#16584):
[WARN] This project requires Node.js 26.10.0. Your current Node.js is v24.18.0
/home/runner/.cache/pnpm
runPnpmCachePath returns all of stdout, so the cache file's path starts with the warning:
the restore misses, because the path is part of the cache version;
the save returns early at !existsSync(cacheFilePath), without logging.
With onFail: "error", pnpm cache path exits with 1, the action falls back to pnpm's default directory, and the cache works. That's why ours broke the day we switched from error to warn.
Activity