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
v6 causes: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. #233
Run pnpm/action-setup@v5
Running self-installer...
Installation Completed!
Restoring cache...
/home/**************/setup-pnpm/node_modules/.bin/pnpm store path --silent
/home/**************/setup-pnpm/node_modules/.bin/store/v10
Error: Some specified paths were not resolved, unable to cache dependencies.
at runRestoreCache (/home/**************/actions-runner/_work/_actions/pnpm/action-setup/v5/dist/index.js:1:917)
at async restoreCache (/home/**************/actions-runner/_work/_actions/pnpm/action-setup/v5/dist/index.js:1:387)
at async runMain (/home/**************/actions-runner/_work/_actions/pnpm/action-setup/v5/dist/index.js:1:2882)
at async main (/home/**************/actions-runner/_work/_actions/pnpm/action-setup/v5/dist/index.js:1:2726)
On GitHub Actions runner (self-hosted):
**********:~/setup-pnpm/node_modules/.bin/store$ ls -al
total 12
drwxr-xr-x 3 **************************** 4096 Apr 24 02:00 .
drwxr-xr-x 5 **************************** 4096 Apr 24 02:00 ..
drwxr-xr-x 5 **************************** 4096 Apr 24 02:00 v11 # Only the v11 directory exists, not the v10 directory.
I have a clean side-by-side repro showing this is a regression in v6, not a pnpm v11 issue, and not a stale-runner artifact.
Both repos use pnpm 11.0.9 (packageManager: pnpm@11.0.9+sha512…) on GitHub-hosted Ubuntu runners, on the same day, with identical actions/setup-node@v6.3.0 + cache: pnpm. The only difference is the pnpm/action-setup version.
pnpm/action-setup@v5.0.0 — succeeds:
[command]/home/runner/setup-pnpm/node_modules/.bin/pnpm store path --silent
/home/runner/setup-pnpm/node_modules/.bin/store/v11
pnpm cache is not found
...
Cache saved with the key: node-cache-Linux-x64-pnpm-
pnpm/action-setup@v6.0.0 — fails:
/home/runner/setup-pnpm/node_modules/.bin/store/v10
pnpm cache is not found
...
##[error]Path Validation Error: Path(s) specified in the action for caching
do(es) not exist, hence no cache is being saved.
So with the exact same pnpm version, v5 reports store/v11 (matches where pnpm actually writes) and v6 reports store/v10 (doesn't exist on disk → setup-node's save step errors out on cache miss).
A subtle factor that hides this for many users: when actions/setup-node's pnpm cache gets a hit, the post-job save step is skipped, so pnpm store path is never validated against the filesystem. The bug only surfaces on a cache miss (e.g. first run after a pnpm-lock.yaml change, or any cold cache). Several of our workflows looked healthy under v6 simply because their cache key hadn't changed yet.
Workaround for now: pin pnpm/action-setup to v5.0.0 (input shape is the same — package_json_file, run_install, etc. all still accepted).
Happy to share full job logs / a minimal reproduction repo if helpful.
This is still happening for me on 6.0.8 with the only change between working and broken CI being the addition of with.cache: true to the pnpm/action-setup uses.
It seems to only happen when there isn't a cache, yet.
Activity
DamdamChoiSE commentedon Apr 24, 2026
I’m experiencing a similar issue as well.
GitHub Actions workflow:
Error message:
On GitHub Actions runner (self-hosted):
KevinNitroG commentedon Apr 26, 2026
I also faced this issue, but it doesn't fail my job. And it doesn't even read my
I have to specify the version for my setup step
ci: downgrade pnpm/action-setup from v6 to v5 in workflows
MindTooth commentedon May 9, 2026
This started to hit us over at https://github.com/srcery-colors/srcery.sh suddenly. Really no clear indication what is causing other than reading posts like this.
maxswjeon commentedon May 11, 2026
I have a clean side-by-side repro showing this is a regression in v6, not a pnpm v11 issue, and not a stale-runner artifact.
Both repos use pnpm 11.0.9 (packageManager: pnpm@11.0.9+sha512…) on GitHub-hosted Ubuntu runners, on the same day, with identical actions/setup-node@v6.3.0 + cache: pnpm. The only difference is the pnpm/action-setup version.
pnpm/action-setup@v5.0.0 — succeeds:
[command]/home/runner/setup-pnpm/node_modules/.bin/pnpm store path --silent
/home/runner/setup-pnpm/node_modules/.bin/store/v11
pnpm cache is not found
...
Cache saved with the key: node-cache-Linux-x64-pnpm-
pnpm/action-setup@v6.0.0 — fails:
/home/runner/setup-pnpm/node_modules/.bin/store/v10
pnpm cache is not found
...
##[error]Path Validation Error: Path(s) specified in the action for caching
do(es) not exist, hence no cache is being saved.
So with the exact same pnpm version, v5 reports store/v11 (matches where pnpm actually writes) and v6 reports store/v10 (doesn't exist on disk → setup-node's save step errors out on cache miss).
A subtle factor that hides this for many users: when actions/setup-node's pnpm cache gets a hit, the post-job save step is skipped, so pnpm store path is never validated against the filesystem. The bug only surfaces on a cache miss (e.g. first run after a pnpm-lock.yaml change, or any cold cache). Several of our workflows looked healthy under v6 simply because their cache key hadn't changed yet.
Workaround for now: pin pnpm/action-setup to v5.0.0 (input shape is the same — package_json_file, run_install, etc. all still accepted).
Happy to share full job logs / a minimal reproduction repo if helpful.
fix: self-update bootstrap to packageManager-pinned version (#233) (#256
kleinfreund commentedon May 27, 2026
This is still happening for me on 6.0.8 with the only change between working and broken CI being the addition of
with.cache: trueto the pnpm/action-setup uses.It seems to only happen when there isn't a cache, yet.
fix(ci): pnpm/action-setup auf v5 zuruecksetzen statt v6
chore(ci): Actions auf node24-faehige Fassungen anheben (#246) (#247)