chore(ci): harden release cache usage (#9588)

.github/workflows/release.yml

@@ -32,9 +32,6 @@ concurrency:
   cancel-in-progress: false
 
 env:
-  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-  TURBO_TEAM: ${{ vars.TURBO_TEAM || github.repository_owner }}
-  TURBO_CACHE: remote:rw
   BETTER_AUTH_TELEMETRY_ENDPOINT: ${{ vars.BETTER_AUTH_TELEMETRY_ENDPOINT }}
 
 jobs:
@@ -69,7 +66,6 @@ jobs:
       - uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
         with:
           node-version-file: '.nvmrc'
-          cache: pnpm
           registry-url: 'https://registry.npmjs.org'
 
       - run: pnpm install --frozen-lockfile
@@ -327,7 +323,6 @@ jobs:
         with:
           node-version-file: '.nvmrc'
           registry-url: 'https://registry.npmjs.org'
-          cache: pnpm
 
       - run: pnpm install --frozen-lockfile
 

.github/zizmor.yml

@@ -8,8 +8,3 @@ rules:
       # Intentional: reads .changeset/*.md content via GitHub API only.
       # No checkout of fork code. No code execution.
       - auto-retarget.yml
-  cache-poisoning:
-    ignore:
-      # False positive: neither setup-node call has caching enabled (no `cache:` param).
-      # The workflow only triggers on tag push, with no shared cache surface.
-      - release.yml