ci: disable fail-fast in weekly toolchain update matrix
What changed, and why it matters
This commit changes two GitHub Actions workflow files so that if one branch's automated toolchain update job fails, the other branches' jobs keep running instead of all being cancelled. It is a pure CI reliability/configuration tweak with no product code changes and no security relevance.
No security action required; this is a routine CI configuration improvement.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change adds fail-fast: false to the matrix strategy in .github/workflows/cron-weekly-update-nightly.yml and .github/workflows/cron-weekly-update-stable.yml. This prevents a failure in one matrix entry (e.g., the 0.32.xxx branch) from cancelling the remaining matrix jobs (master and 0.32.xx). No Rust source code, dependencies, cryptographic logic, or build outputs are modified.
Changed components
.github/workflows/cron-weekly-update-nightly.yml.github/workflows/cron-weekly-update-stable.ymlInspect captured patch +2 / −0
### .github/workflows/cron-weekly-update-nightly.yml
@@ -13,6 +13,7 @@ jobs:
id-token: write
pull-requests: write
strategy:
+ fail-fast: false
matrix:
# Update toolchain on master and LTS branches.
branch: [master, 0.32.xxx, 0.32.xx]
### .github/workflows/cron-weekly-update-stable.yml
@@ -12,6 +12,7 @@ jobs:
contents: write
pull-requests: write
strategy:
+ fail-fast: false
matrix:
# Update toolchain on master and LTS branches.
branch: [master, 0.32.xxx, 0.32.xx]Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.