Stable release cut no longer waits on the Windows nightly (GST-2815) (#4400)

* Stable release cut no longer waits on the Windows nightly (GST-2815)

The nightly Windows free suite is documented as never gating, but the
daily cut refused any commit carrying its red or unfinished check runs, so
stable stayed behind v1.99.5.0 while shard 4 kept timing out. The cut now
sets that workflow's check runs aside by workflow path, like its own job.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Type the expected green verdict in the nightly test as a literal

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
Garry Tanandcapy-ai[bot] authored and GitHub committed 2026-11-16 02:46:26 +00:00
1 parent 0326b144af
commit 45ee345030
5 files changed
+48 -7

No files matched your search

+4 -1
View File
@@ -50,7 +50,10 @@ days or 200 first-parent commits. The cut's own job lands a check run on
main's head, the very commit it may cut, so check runs from this workflow's
own runs (its file path, `.github/workflows/weekly-release.yml`, matched
by the job ids of those workflow runs) are set aside whether running or
failed; every other check run counts as above. The lookup needs the
failed. Check runs from the nightly Windows free suite
(`.github/workflows/windows-free-tests.yml`), which
[never blocks](support-tiers.md#windows-ci), are set aside the same way;
every other check run counts as above. The lookup needs the
workflow's `actions: read` permission; when it cannot read those runs, nothing
is set aside. The workflow runs no tests and no paid evals
of its own; it only reads what the trains, the backstop and the release gate
+1 -1
View File
@@ -24,7 +24,7 @@ That is the whole promise. Other skills, optional parts such as `/cso`'s native
## Windows CI
- `windows-smoke` is the required Windows check on pull requests.
- The six-shard Windows free suite (the `Windows Free Tests` workflow, `windows-free-tests`) runs nightly on main, or when someone starts it by hand, and never blocks a pull request.
- The six-shard Windows free suite (the `Windows Free Tests` workflow, `windows-free-tests`) runs nightly on main, or when someone starts it by hand, and never blocks a pull request. The stable release cut ignores its results too, so a red or unfinished nightly never holds a release.
- A red nightly run gets a fix only when it shows an install, startup or core-workflow break.
- Windows checks run by path (ship-90-90 plan D, approved 2026-11-03): `Windows Scoped Tests` runs a pull request's changed Windows-safe test files on one Windows job only when it touches path, file-name or process code (a red run blocks that pull request, like any failed check), and `Windows Setup E2E` runs only when install files change (a version-only `package.json` change doesn't count).