GitHub Actions macOS 14 runners retire on November 2
Move pinned macOS 14 workflows before GitHub’s brownout windows start breaking jobs.
Short answerMove off macOS 14 now; choose macOS 15 for stability, or macOS latest if you accept a moving runner target.
By JasonPublished Oct 2, 2026Last verified Oct 2, 20264 min read
If your GitHub Actions workflows still pin macOS 14, the decision is no longer whether to migrate, but how narrowly to migrate. GitHub Changelog says the macOS 14 runner image will be retired on November 2, 2026, and it names three affected labels: macos-14, macos-14-large, and macos-14-xlarge. Before that date, GitHub will run scheduled brownouts in October where jobs using those labels temporarily fail. GitHub also says capacity may be reduced during the lead-up, which can mean longer queue times for teams that wait.
For indie builders and remote teams, the practical question is which label to use next. GitHub’s notice points arm64 workflows toward macos-latest, macos-15, macos-latest-xlarge, or macos-15-xlarge, with macos-latest currently mapped in the notice to macos-26. The trade-off is stability versus freshness: a fixed macOS 15 label gives you a more explicit migration target, while macos-latest follows GitHub’s moving default. The key work before the first brownout is to find all pinned macOS 14 labels, decide whether each job needs a fixed or moving image, and run the workflow before the retirement date forces the change.
What is changing
According to GitHub Changelog, the macOS 14 runner image for GitHub Actions is scheduled for retirement on November 2, 2026. The affected labels are `macos-14`, `macos-14-large`, and `macos-14-xlarge`.
GitHub says jobs using those labels will temporarily fail during several October brownout windows. The listed windows run from 14:00 UTC to 00:00 UTC across these start dates: October 5, October 12, October 16, October 19, October 23, October 26, October 29, and October 30.
GitHub also says it may reduce macOS 14 runner capacity before retirement, so workflows that stay on those labels may see longer queues.
What to change
GitHub’s notice tells users to update workflows to one of these macOS arm64 labels:
- `macos-latest`, identified in the notice as `macos-26`
- `macos-15`
- `macos-latest-xlarge`, identified in the notice as `macos-26-xlarge`
- `macos-15-xlarge`
The editorial choice is not just old label versus new label. It is fixed label versus moving label.
Choose `macos-15` or `macos-15-xlarge` if you want the migration to be explicit and easier to review in pull requests. Choose `macos-latest` or `macos-latest-xlarge` if your team is comfortable following GitHub’s current default image as it changes.
Migration checklist
- Search workflow files for `macos-14`, `macos-14-large`, and `macos-14-xlarge`.
- Replace each label with either a fixed macOS 15 label or a latest label.
- Prioritize release, signing, packaging, and mobile build workflows before lower-risk CI jobs.
- Run the changed workflows before the first listed brownout.
- If a workflow fails after migration, use GitHub’s runner images repository for current tool and software details, as GitHub Changelog directs.
Benchdict view
Do not wait for the November 2 retirement date. The brownouts are designed to make pinned macOS 14 usage visible by breaking jobs temporarily. If a workflow is part of a release path, treat the first October brownout as the real deadline.
Our read: this is a small YAML change only if your CI does not depend on the exact macOS image contents. The deadline itself is clear because GitHub is the platform owner and has named both the retirement date and the labels being removed. The risk is in the parts not spelled out in the changelog: whether your builds depend on specific tooling inside the macOS 14 image, and whether switching to a newer image changes signing, build, packaging, or test behavior.
For most teams, the safer migration path is not simply replacing every label with `macos-latest`. Use `macos-15` or `macos-15-xlarge` when you want a more explicit target and fewer surprises from a moving alias. Use `macos-latest` only when staying on GitHub’s current default is part of your maintenance model. The brownout schedule is useful as a forcing function, but it is a poor time to discover that a release workflow depended on a removed image.
Move off macOS 14 now; choose macOS 15 for stability, or macOS latest if you accept a moving runner target.
GitHub’s own changelog makes the retirement date and affected labels clear, but the right replacement depends on whether your team values a fixed image label or GitHub’s moving latest alias.
Teams with no GitHub Actions workflows using the named macOS 14 labels do not need this migration.
Read next
Follow new articles
Email updates are not live yet, and we are not collecting addresses. To follow new articles, use the RSS feed.