Development record
The release path runs no macOS suite, though the product thinker ruled that each release cut runs its own before releasing, whatever the nightly said. With macOS out of the merge queue, a macOS-only regression merged after a nightly run could be tagged and published on Linux checks alone, since every job in release.yml and auto-release.yml runs on ubuntu and a red nightly stops nothing.
issueresolvedmajoriss-2611042224527148
The release path runs no macOS suite, though the product thinker ruled that each release cut runs its own before releasing, whatever the nightly said. With macOS out of the merge queue, a macOS-only regression merged after a nightly run could be tagged and published on Linux checks alone, since every job in release.yml and auto-release.yml runs on ubuntu and a red nightly stops nothing.
Frontmatter
| id | iss-2611042224527148 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2611042224527148-release-path-runs-no-macos-suite.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26110422025093342026-11-04 — The product thinker ruled on 2026-11-04 that the merge queue runs Linux on every entry and hosted macOS runs nightly and on demand, after a day on which queue entries kept dropping because GitHub had no macOS runner to give, with no test failing. Each release cut also runs its own macOS suite before releasing, whatever the nightly said. The release path runs it: release.yml's tag and publish jobs need a gate over the shards it runs on the commit it is about to tag (iss-2611042224527148). A self-hosted runner is held for later, if one is ever needed.