Announcement date: 1 October 2026. GitHub announced the retirement of GitHub Actions runner images based on macOS 14. This is not trivia about an operating-system number. For a pipeline that builds and signs applications, it is an expiry date for part of the execution environment.

What GitHub announced

  • images selected by macos-14, macos-14-large and macos-14-xlarge are scheduled for retirement on 2 November 2026;
  • GitHub plans brownouts on 5, 12, 16, 19, 23, 26, 29 and 30 October;
  • the recommended migration is to macos-latest or macOS 15 arm64 runners, depending on the job's requirements;
  • macOS 14 runner capacity may be reduced during the retirement period, which can increase queue time.

These are facts from the GitHub Changelog published on 1 October 2026. Check the exact toolset for replacement images in actions/runner-images.

Architecture interpretation

Inventory workflows, reusable workflows and actions that may select these labels indirectly. Then run representative builds on the target image: compile, test, package, sign and publish. A green unit-test job does not prove that the final release step works.

Moving to macos-latest reduces manual migrations but lets GitHub advance the image version. That is a deliberate trade-off, not free stability. If a compiler, Xcode version or signing tool is part of a controlled supply chain, pin it explicitly and observe image updates.

The pipeline needs an owner, a migration date, a test and a fallback. A runner is a production dependency even though it serves no user traffic. Without it, you cannot ship a fix — a fact that tends to become interesting only during an incident.

Question for your project: can you identify every pipeline that depends on the macOS 14 image and prove that an artifact from the replacement image can also be signed and published?

Primary sources: GitHub Changelog, 1 October 2026; GitHub Actions runner images. “Architecture interpretation” is the author's analysis.