timetobail
My stack

GitHub Actions · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on GitHub Actions jobs on macos-14?

Time to Bail · Boarding pass

FromGitHub Actions jobs on macos-14
ToYour pick

Act. You can stay.

Macos-14 jobs end with an error after November 2, 2026. Change the runner label.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Fully unsupported
Time left
17days
Status
Act

GitHub Actions macos-14 runners retire November 2, 2026

GitHub retires the macos-14 runner images on November 2, 2026. Jobs that still use them end with an error. Short planned outages already make these jobs fail on some days in October.

How it is winding down

  1. Jul 6Deprecation beganDone
  2. Nov 2Fully unsupportedNext

What to do before November 2

Tick steps as you go. Your progress stays in this browser.

  1. Search your workflows

    Look for runs-on: macos-14 in .github/workflows in every repo.

  2. Change the label

    Use macos-15, macos-26 or macos-latest. For large runners use the matching -large or -xlarge label.

  3. Fix Xcode and tool versions

    A newer image has newer Xcode and tools. Run the job once and fix what breaks.

Facts we checked

Facts and their sources
Fully unsupportedNovember 2, 2026[1]
Labelsmacos-14, macos-14-large and macos-14-xlarge[1]
If you do nothingWorkflows using these labels will be terminated with an error[1]
Planned outages (brownouts)October 16, 19, 23, 26, 29 and 30, 14:00 to 00:00 UTC; jobs fail then[1]
Deprecation beganJuly 6, 2026[1]
Replace withmacos-latest, macos-15 or macos-26 (and the matching -large or -xlarge labels)[1]
Also affectsAzure DevOps hosted agents[1]
Workflows on macos-14Fail after November 2, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. The macOS 14 Sonoma image is closing down GitHub · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on GitHub Actions jobs on macos-14? Act. You can stay. Macos-14 jobs end with an error after November 2, 2026. Change the runner label.

On our scale this is Act: change a setting or plan before the date. You can stay.

GitHub retires the macos-14 runner images on November 2, 2026. Jobs that still use them end with an error. Short planned outages already make these jobs fail on some days in October.

Here are the facts we checked:

  • Fully unsupported: November 2, 2026 (GitHub)
  • Labels: macos-14, macos-14-large and macos-14-xlarge (GitHub)
  • If you do nothing: Workflows using these labels will be terminated with an error (GitHub)
  • Planned outages (brownouts): October 16, 19, 23, 26, 29 and 30, 14:00 to 00:00 UTC; jobs fail then (GitHub)
  • Deprecation began: July 6, 2026 (GitHub)
  • Replace with: macos-latest, macos-15 or macos-26 (and the matching -large or -xlarge labels) (GitHub)
  • Also affects: Azure DevOps hosted agents (GitHub)
  • Workflows on macos-14: Fail after November 2, 2026 (GitHub)

You can stay on GitHub Actions. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

GitHub is the main source for this page. GitHub Actions has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Workflows on macos-14: Fail after November 2, 2026.

The date to remember is November 2, 2026. Make the change before then.

What to do before November 2

  1. Search your workflows. Look for runs-on: macos-14 in .github/workflows in every repo.
  2. Change the label. Use macos-15, macos-26 or macos-latest. For large runners use the matching -large or -xlarge label.
  3. Fix Xcode and tool versions. A newer image has newer Xcode and tools. Run the job once and fix what breaks.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on GitHub Actions jobs on macos-14 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product