Repository navigation
fix(ci): pin Node releases with incident key rejection - #281
Merged
Merged
Conversation
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
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.
What Problem This Solves
Managed website and translation jobs can select cached Node versions that trust the compromised eMudhra keys.
User Impact
Pin Node 26.12.1 within the existing release line. Installed products and the Actions runner require separate updates.
Why This Change Was Made
Exact fixed patches prevent old cache entries from satisfying setup-node, including its fallback after manifest-resolution failure.
Evidence
Changed workflows passed duplicate-key YAML validation. Unchanged application and Go suites were not rerun. Independent review and
git diff --checkpassed. Official Linux arm64 release binaries rejected all 12 incident chains in eight trust modes, with ordinary HTTPS controls passing. Other platform executions remain hosted CI proof.