Install Yarn in the frontend CI job instead of relying on setup-node's cache #89
Reference in New Issue
Block a user
Delete Branch "fix/ci-frontend-yarn"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every frontend CI run since the workflow was added (#78) failed at actions/setup-node: its cache: yarn option needs yarn already on PATH, and the Node 22.14.0 it installs ships without one (the log shows 'yarn:' empty, then the failure). The backend job has been passing. Now that main requires checks, this blocks every merge.
Fix: drop cache: yarn and install Yarn 1.22.22 (the lockfile's version) with npm before the frozen install.
Verified by running the frontend job's steps in a clean node:22.14.0 container: yarn 1.22.22 installs, the frozen lockfile install succeeds, 20 renderer tests pass, tsc passes, and the build succeeds. This PR's own CI run is the final check.
🤖 Generated with Claude Code