Live
Local Artifacts Support Lets Workers Test Repo Workflows Before DeployCo‑Packaged Optics Cut Power Use and Latency in Lambda’s 10k‑GPU AI ClusterScaling AI Agents on Kubernetes: New CNCF Projects and Operational ImplicationsGitHub Copilot model deprecation forces updates to AI‑assisted development pipelinesGitHub Copilot expands Enterprise Server access and adds new AI models – practical impact for engineersArchitecting Agentic Customer Engagement with Amazon Bedrock AgentCoreBuilding Multi‑Tenant Memory‑Aware Agents with Bedrock Agentic Retrieve and Managed Knowledge BaseBulk‑Start AI Scan for Up to 20 GitHub Repos: What Engineers Need to KnowLocal Artifacts Support Lets Workers Test Repo Workflows Before DeployCo‑Packaged Optics Cut Power Use and Latency in Lambda’s 10k‑GPU AI ClusterScaling AI Agents on Kubernetes: New CNCF Projects and Operational ImplicationsGitHub Copilot model deprecation forces updates to AI‑assisted development pipelinesGitHub Copilot expands Enterprise Server access and adds new AI models – practical impact for engineersArchitecting Agentic Customer Engagement with Amazon Bedrock AgentCoreBuilding Multi‑Tenant Memory‑Aware Agents with Bedrock Agentic Retrieve and Managed Knowledge BaseBulk‑Start AI Scan for Up to 20 GitHub Repos: What Engineers Need to Know
GitHub

Migrate GitHub Actions Workflows Ahead of macOS 14 Runner Retirement

AI SummaryPowered by AI

GitHub is retiring the macOS 14 runner image on 2026-11-02 and will temporarily fail jobs using it during scheduled brownouts in October. Practitioners must update workflows to newer macOS labels to keep CI pipelines reliable and avoid longer queue times.

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 (alias macos-26)
  • macos-15
  • macos-latest-xlarge (alias macos-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:

  1. Audit all GitHub Actions workflows for the three deprecated macOS 14 labels.
  2. Replace them with one of the four supported labels before the first brownout window to avoid forced failures.
  3. Monitor queue times for macOS jobs after the migration; consider scaling parallelism or using larger runner sizes if capacity becomes constrained.
  4. 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.

Originally published atGitHub Changelog