https://www.cloudkaramchari.com/tags/xcode/Recent content in Xcode on CloudkaramchariHugo -- gohugo.ioencloudkaramchariSun, 04 Oct 2026 14:30:00 +0530https://www.cloudkaramchari.com/blog/github-actions-macos-14-runner-retirement-migration-guide-brownouts-october-2026/Sun, 04 Oct 2026 14:30:00 +0530https://www.cloudkaramchari.com/blog/github-actions-macos-14-runner-retirement-migration-guide-brownouts-october-2026/ <h1 id="github-actions-macos-14-runner-retirement-survive-the-october-brownouts-and-migrate-before-november-2">GitHub Actions macOS 14 Runner Retirement: Survive the October Brownouts and Migrate Before November 2</h1> <p>Starting <strong>October 5, 2026 at 14:00 UTC</strong>, GitHub will deliberately fail every job that asks for a macOS 14 hosted runner, for ten hours at a time, on eight separate days this month. On <strong>November 2, 2026</strong> the image goes away permanently. If any workflow in your organization still says <code>runs-on: macos-14</code> (or <code>macos-14-large</code> / <code>macos-14-xlarge</code>), it has a scheduled outage on your calendar whether you put it there or not. The label swap itself is one line. The reason teams get burned is everything that line was silently pinning: Xcode 15, the iOS 17 simulators, and an x64 vs arm64 choice that the replacement labels make differently.</p>