6.0.8 post run error on cold cache: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
Previously seen in https://github.com/pnpm/action-setup/issues/233
On a GitHub workflow run with the only change being the addition of with.cache: true on the pnpm/action-setup action, I'm consistently running into this error in the post run job:
Post job cleanup.
Pruning is unnecessary.
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
This reproduces reliably provided there isn't already a cache from the same workflow running previously without with.cache: true.
Context
- action version 6.0.8
- pnpm version 10.34.1 (the setup action prints
Switching pnpm from v11.1.1 to v10.34.1...) - Doesn't happen when running pnpm version 11
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 reproducing the pnpm/action-setup workflow with with.cache: true on version 6.0.8, pnpm 10.34.1, and a cold cache. Compare the post-job cleanup behavior with pnpm 11 and inspect the action's cache entry point. Done means the cold-cache run completes without the path validation error and saves the cache when appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100