Repository navigation
chore(ci): explicitly disable setup-node cache in release and supply-chain workflows (AI-assisted) - #12479
Merged
Conversation
…chain workflows (AI-assisted) Follows actions/setup-node v7 guidance (actions/setup-node#1567) to set `package-manager-cache: false` in privileged workflows to mitigate cache poisoning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
⚡️ Lighthouse report for the deploy preview of this PR
|
slorber
deleted the
claude/github-actions-node-cache-security-eb54a8
branch
September 24, 2026 10:17
1 of 3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pre-flight checklist
Motivation
Audit of our
actions/setup-nodecaching against v7.0.0 and its cache poisoning recommendations (actions/setup-node#1567).Current state is safe: no
pull_request_target/workflow_run/issue_commenttriggers, PR caches are scoped to their PR ref, and release workflows (publish.yml,continuous-releases.yml) don't restore any cache. setup-node auto-caching only triggers for npm (we use pnpm), andpnpm/action-setupcaching is off by default.This PR adds an explicit
package-manager-cache: falseto the no-cache workflows (publish, continuous releases, supply chain security) as defense-in-depth, so caching can't silently turn on if auto-detection behavior or our package manager changes.(AI-assisted)
Test Plan
CI
Test links
Deploy preview: https://deploy-preview-12479--docusaurus-2.netlify.app/
Related issues/PRs
🤖 Generated with Claude Code