From bd4b8936e463b6f409e8e721e2f06db658143d0a Mon Sep 17 00:00:00 2001 From: Ryan Chen Date: Tue, 13 Oct 2026 08:36:03 -0400 Subject: [PATCH] Install Yarn in the frontend CI job instead of relying on setup-node's cache setup-node's `cache: yarn` needs yarn already on PATH, and the Node it installs does not ship one, so the frontend job failed at setup on every run. Install the lockfile's Yarn 1.22.22 explicitly instead. Co-Authored-By: Claude Opus 5.5 --- .gitea/workflows/ci.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index 05fbc34..214a8aa 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -34,11 +34,13 @@ jobs: working-directory: raggr-frontend steps: - uses: actions/checkout@v4.2.2 + # No `cache: yarn` here: setup-node requires yarn to already be on PATH + # for that, and the Node it installs doesn't ship one. - uses: actions/setup-node@v4.4.0 with: node-version: '22.14.0' - cache: yarn - cache-dependency-path: raggr-frontend/yarn.lock + - name: Install Yarn (lockfile v1) + run: npm install --global yarn@1.22.22 - name: Install locked frontend dependencies run: yarn install --frozen-lockfile - name: Renderer tests -- 2.52.0