Retirement Timeline and Scheduled Brownouts

According to the official [GitHub Changelog](https://github.blog/changelog/2026-10-01-github-actions-macos-14-runner-image-retirement/), the macOS 14 runner image is officially set to be retired on November 2, 2026. To ensure that users and development teams are fully aware of the upcoming removal, GitHub has planned a series of scheduled brownout periods during which jobs relying on macOS 14 will temporarily fail.

These planned brownout periods are distributed throughout October 2026 to highlight any lingering dependencies before the final sunset date. The scheduled times include October 12 from 14:00 UTC to October 13 at 00:00 UTC, October 16 from 14:00 UTC to October 17 at 00:00 UTC, and October 19 from 14:00 UTC to October 20 at 00:00 UTC.

Additional brownout windows are scheduled for October 23 from 14:00 UTC to October 24 at 00:00 UTC, October 26 from 14:00 UTC to October 27 at 00:00 UTC, October 29 from 14:00 UTC to October 30 at 00:00 UTC, and a final window on October 30 from 14:00 UTC to October 31 at 00:00 UTC.

Impact on Capacity and Queue Times

As the platform moves closer to the retirement date, developers utilizing the affected environment should expect operational adjustments. GitHub has stated that it may reduce macOS 14 runner capacity during the lead-up to the final removal date.

This reduction in available capacity could result in significantly longer queue times for any jobs that continue to utilize the targeted macOS 14 labels. Teams are therefore encouraged to audit their current infrastructure configurations early to avoid unnecessary pipeline delays.

Recommended Developer Actions and Updates

To maintain seamless continuous integration and deployment pipelines, developers must update their workflow files. Specifically, projects should transition away from the deprecated configuration and adopt one of the supported macOS arm64 labels.

For teams looking to verify the most up-to-date information regarding available software tools and environment specifications, resources can be found by checking the [runner images repository](https://github.com/actions/runner-images). Keeping workflows aligned with supported configurations ensures long-term stability.

Support and Additional Resources

Development teams that encounter unexpected issues, technical blockers, or require further assistance during this transition period are advised to reach out directly through [GitHub Support](https://support.github.com/contact?form%5Bsubject%5D=Re%3A+GitHub+Actions&tags=dotcom-contact-params).

Additionally, developers can continue to follow platform updates, technical guides, and best practices across the broader ecosystem by reviewing ongoing announcements and community resources provided by the platform.

Sources

• GitHub ChangelogGitHub Actions: macOS 14 runner image retirement