Skip to content

fix: disable setup-node v5 auto-cache (pnpm not yet installed)#395

Merged
bearpong merged 1 commit into
mainfrom
fix/setup-node-cache
May 27, 2026
Merged

fix: disable setup-node v5 auto-cache (pnpm not yet installed)#395
bearpong merged 1 commit into
mainfrom
fix/setup-node-cache

Conversation

@qtipbera
Copy link
Copy Markdown
Contributor

this PR unblocks #392 and needs an admin bypass.

actions/setup-node@v5 introduced automatic package manager caching — when it detects a packageManager field in package.json, it tries to resolve and cache that package manager before any other steps run. Since pnpm/action-setup runs AFTER setup-node, pnpm isn't on PATH yet and the step fails with:

Error: Unable to locate executable file: pnpm

This is a known v5 breaking change: actions/setup-node#1351

Fix: add package-manager-cache: false to all setup-node steps. The workflow already has manual actions/cache steps for the pnpm store, so the auto-cache is redundant anyway.

@bearpong Same chicken-and-egg as the lockfile fix — pull_request_target runs main's workflow, so this needs an admin-bypass merge to unblock CI. One-line addition per job, no behavioral changes.

@qtipbera qtipbera changed the title fix: disable setup-node v5 auto-cache (pnpm not yet installed fix: disable setup-node v5 auto-cache (pnpm not yet installed) May 26, 2026
@bearpong bearpong merged commit 3a36fa1 into main May 27, 2026
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants