The macOS 14 runner image for GitHub Actions will be retired on 2026-11-02, and GitHub will temporarily fail jobs that target this image during a series of scheduled brownout windows in October. Teams that rely on macOS‑based CI/CD need to adjust their workflows now to avoid unexpected failures and potential queue delays as capacity for the retiring image is reduced.
What Changed
GitHub announced the deprecation of three macOS 14 runner labels: macos-14, macos-14-large, and macos-14-xlarge. The retirement date is 2 November 2026. To draw attention, jobs using these labels will be forced to fail during the following brownout periods (all times UTC):
- 2026‑10‑05 14:00 – 2026‑10‑06 00:00
- 2026‑10‑12 14:00 – 2026‑10‑13 00:00
- 2026‑10‑16 14:00 – 2026‑10‑17 00:00
- 2026‑10‑19 14:00 – 2026‑10‑20 00:00
- 2026‑10‑23 14:00 – 2026‑10‑24 00:00
- 2026‑10‑26 14:00 – 2026‑10‑27 00:00
- 2026‑10‑29 14:00 – 2026‑10‑30 00:00
- 2026‑10‑30 14:00 – 2026‑10‑31 00:00
Impact on CI/CD Pipelines
During the brownouts, any workflow that still references the retired labels will see immediate failures, which can break release pipelines, automated testing, or model‑training jobs that depend on macOS environments. In the weeks leading up to retirement, GitHub may also shrink the available pool of macOS 14 runners, causing longer queue times for jobs that have not yet migrated.
Migration Path
Update workflow files to target one of the supported macOS arm64 labels:
macos-latest(aliasmacos-26)macos-15macos-latest-xlarge(aliasmacos-26-xlarge)macos-15-xlarge
These labels point to the newer runner images that will continue to receive updates. For the most current list of tools and software versions, consult the runner images repository referenced in the announcement. If migration introduces unexpected behavior, GitHub Support is the recommended contact point.
Related CloudNinjas coverage: DevOps.
What This Means For Practitioners
Action items:
- Audit all GitHub Actions workflows for the three deprecated macOS 14 labels.
- Replace them with one of the four supported labels before the first brownout window to avoid forced failures.
- Monitor queue times for macOS jobs after the migration; consider scaling parallelism or using larger runner sizes if capacity becomes constrained.
- Keep an eye on the runner images repository for any further changes to macOS image availability.
By completing these steps, AI engineers, platform engineers, DevOps/SRE staff, and security engineers can maintain reliable CI pipelines and avoid disruption to macOS‑dependent automation.