Skip to content

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

Closed
NEERC/volunteers-py
#32

Description

@Jason3S

After upgrading from v5 to v6, workflows started failing due to caching issues. Rolling back to v5 fixes the issue.

Image

Note: The version of pnpm is stored in package.json:

  "packageManager": "pnpm@10.29.2+sha512.bef43fa759d91fd2da4b319a5a0d13ef7a45bb985a3d7342058470f9d2051a3ba8674e629672654686ef9443ad13a82da2beb9eeb3e0221c87b8154fff9d74b8",

Activity

  1. DamdamChoiSE commented on Apr 24, 2026

    @DamdamChoiSE

    I’m experiencing a similar issue as well.

    GitHub Actions workflow:

        steps:
          - name: Checkout
            uses: actions/checkout@v6
    
          - name: Install node
            uses: actions/setup-node@v6
            with:
              node-version: 24
    
          - name: Install pnpm
            uses: pnpm/action-setup@v6
            with:
              version: 10    # pnpm version v10
              cache: true
    

    Error message:

    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.
  2. KevinNitroG commented on Apr 26, 2026

    @KevinNitroG

    I also faced this issue, but it doesn't fail my job. And it doesn't even read my

      "devEngines": {
        "packageManager": {
          "name": "pnpm",
          "version": "10.28.2",
          "onFail": "warn"
        }
      },
      "packageManager": "pnpm@10.28.2"

    I have to specify the version for my setup step

  3. MindTooth commented on May 9, 2026

    @MindTooth

    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.

  4. maxswjeon commented on May 11, 2026

    @maxswjeon

    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.

  5. kleinfreund commented on May 27, 2026

    @kleinfreund

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions