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
Description:
The Node.js version should be included in the cache key. The major version number, (e.g., 22 in 22.12) should be used to avoid unnecessary invalidation when upgrading to patch or minor versions.
Justification:
Some dependencies need to be rebuilt for specific Node versions. Reusing the cache for an older version results in dependency installation failures.
Any new on this issue ?
In monorepo with packages to test with different Node.js, applications not all with the same Node.js version, the actual generated key lead to dependencies which need to be rebuilt each time.
Activity
v-gowridurgad commentedon Dec 16, 2024
Hello @clintonb ,
Thank you for this feature request. We will investigate it and get back to you as soon as we have some feedback.
tpoisseau commentedon May 13, 2025
Any new on this issue ?
In monorepo with packages to test with different Node.js, applications not all with the same Node.js version, the actual generated key lead to dependencies which need to be rebuilt each time.
ayeshasaeed665 commentedon Nov 3, 2025
Any new update on the issue?
Kunal-kumar2 commentedon Jan 27, 2026
Any new update on the issue?
fix(ci): rebuild better-sqlite3 after pnpm cache restore to fix Node …