Repository navigation
fix(ci): propagate exhausted npm install failures - #14369
Merged
Merged
Conversation
This was referenced Sep 21, 2026
diegosouzapw
marked this pull request as ready for review
September 24, 2026 00:42
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.
Problem and change
When all three
npm ciattempts fail, the composite action captures the status ofthe completed
ifstatement (zero). Downstream jobs then continue without installeddependencies and the cache-miss path appears successful. Capture the npm exit in
the
elsebranch so the final failed attempt fails the composite.Validation
06f1df9d775d: the actual Bash action returned 0 for41,42,43and42,42,42.build fail-closed, the full quality profile and required verdict rollout are separate
items in the authorized recovery plan. Full release-green is not claimed here.