bug: Cache restore failure in v4.3.0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the pnpm/action-setup@v4.2.0 and @v4.3.0 behavior in the shown workflow, focusing on the cache restore step and the cache_dependency_path setting. Reproduce the pnpm store path --silent and unresolved-path error, then verify that the workflow restores its cache successfully with the newer release or document the confirmed regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, typescript
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100