3e94044550
The rolling-bootstrap workflow only triggered on master, so a risky change could not be proven against the bootstrap chain before merging — and a bad commit on master cannot be removed without a force-push on a public repo. Trigger the workflow on push to ci/**, feature/** and bootstrap/** branches (plus master and the existing workflow_dispatch). Branch runs are VALIDATE-ONLY: - The carry-forward cache (stage + save steps) is written ONLY on refs/heads/master, so a branch never overwrites master's resume anchor and a broken branch's -pre binary can never leak into a later master run. - Branch runs still restore the cache read-only, so a branch off recent master resumes from master's latest good -pre and replays only its own new commits; a diverged branch falls back to the cold-start anchor as before. - The -pre artifact upload still runs on branches (keyed by commit SHA, so it never collides with master's and is pull-only). concurrency is already keyed on github.ref, so per-branch runs don't cancel each other or master. Note: this only takes effect once pushed, so like the other Phase 4 CI changes it cannot be exercised until the v0.12.0 cut. |
||
|---|---|---|
| .. | ||
| workflows | ||
| FUNDING.yml | ||