E2E's setup-node caches nothing by leaving cache unset

setup-node v4 reads `cache` as a package-manager name, so `cache: false` asked it to cache for a manager called "false" and it failed the step with "Caching for 'false' is not supported". Leaving the input unset is how v4 caches nothing, which is what the setting meant. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-23 05:57:59 -07:00
parent 894fa7ccde
commit 85a385ebf6
1 changed files with 0 additions and 4 deletions
@@ -38,7 +38,6 @@ jobs:
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
-          cache: false
          node-version: ${{ env.NODE_VERSION }}

      - name: Install dependencies
@@ -80,7 +79,6 @@ jobs:
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
-          cache: false
          node-version: ${{ env.NODE_VERSION }}

      - name: Install dependencies
@@ -130,7 +128,6 @@ jobs:
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
-          cache: false
          node-version: ${{ env.NODE_VERSION }}

      - name: Install dependencies
@@ -174,7 +171,6 @@ jobs:
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
-          cache: false
          node-version: ${{ env.NODE_VERSION }}

      - name: Install dependencies