bug: Cache restore failure in v4.3.0

[brionmario]

Our CI pipelines suddenly started failing after v4.3.0 of pnpm/action-setup was released with the following error during the cache restore step:

Restoring cache...
/home/runner/setup-pnpm/node_modules/.bin/pnpm store path --silent
/home/runner/setup-pnpm/node_modules/.bin/store/v10
Error: Some specified paths were not resolved, unable to cache dependencies.

Pinning the action to v4.2.0 resolves the issue, and the workflow runs successfully again.

- name: 📦 Install pnpm
  uses: pnpm/action-setup@v4.2.0
  with:
    version: "latest"
    run_install: false
    cache_dependency_path: frontend/pnpm-lock.yaml

This workflow has been working reliably prior to v4.3.0, so this appears to be related to the latest release.

Are we using the action incorrectly here, or could this be a regression introduced in v4.3.0?

[nortolan-avb]

We were experiencing the same error in our CI pipelines with the following configuration, and we've also pinned v4.2.0 to resolve it for now.

- name: Set up pnpm
  uses: pnpm/action-setup@v4
  with:
    version: 10
    cache: true

We are using self-hosted GHA runners and are seeing this path when pnpm store path --silent is run within getCacheDirectory:
/home/runner/setup-pnpm/node_modules/.bin/store/v10

[zkochan]

Must be related to #188

[glektarssza]

Still seeing this in v5.0.0 and the following settings:

package_json_file: package.json
run_install: false
standalone: false
cache: true

This is about the most simplistic setup possible.

Could this have something to do with pnpm/pnpm#10490? This was merged after #188 got tested and merged and I could see it having impacted the functionality behind #188.

Edit: Typo 😅