ci: use the runner image's node instead of setup-node, which downloaded it again on every run

2026-10-21 18:53:42 +02:00
parent 7e0664250b
commit 2a06239676
4 changed files with 23 additions and 24 deletions
@@ -271,12 +271,14 @@ jobs:
          GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
        run: ./zig-out/bin/release resolve

-      - name: Set up Node
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
+      # The runner image ships this Node and npm on PATH; the assertion below is
+      # what pins them. setup-node is not used: it looks for Node in an empty
+      # tool cache and downloads it again on every run.
+      - name: Cache npm downloads
+        uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
        with:
-          node-version: ${{ env.NODE_VERSION }}
-          cache: npm
-          cache-dependency-path: admin/package-lock.json
+          path: ~/.npm
+          key: npm-${{ runner.os }}-${{ hashFiles('admin/package-lock.json') }}

      # The same pinned toolchain and normalized environment as the frontend
      # job in gates.yml: the cut pinned the bundle's bytes into flake.nix