setup-node v5 fails with Path Validation Error in Post Run steps - change error to warning?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Upgrading to setup-node v5 causes a a workflow to fail with the following error:
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
According to https://github.com/actions/setup-node/issues/1363 the underlying code is in this repository. Not saving a cache doesn't seem like an error that should fail the job, but simply a warning that should be logged. Can this be changed so upgrading to setup-node v5 doesn't require additional changes?
To Reproduce
Steps to reproduce the behavior:
- Failing PR: https://github.com/Lullabot/drainpipe/pull/935
- Failing job: https://github.com/Lullabot/drainpipe/actions/runs/17513511413/job/49761979980?pr=935
Expected behavior
The job doesn't fail for running npx tools directly.
Thanks!
Contributor guide
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
The issue does not name a file or test; start with the underlying setup-node code referenced in actions/setup-node#1363 and reproduce the linked workflow failure. Done means a missing cache path in a post-run step produces a warning rather than failing the job, while the npx workflow completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, 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