On 12 November 2026 GitHub posted a retirement notice: hosted GitHub Actions runners will stop supporting ARM32 job execution on both Windows and Linux by 8 December 2026.
What GitHub says
- What is going. ARM32 job execution on GitHub-hosted Linux and Windows runners, including native AArch32 user-space execution.
- Why. GitHub ties it to the end of support for Node 20. Node 24, the replacement, does not support ARM32.
- When. By 8 December 2026, less than four weeks after the notice.
Why a non-developer should care
ARM32 is the older 32-bit chip design. Most current phones and laptops have moved on, but it still sits inside industrial equipment, kiosks, older Android hardware and embedded devices. If your product has to run on any of those, the automated build and test pipeline behind it may depend on exactly the runners GitHub is switching off.
This is also a pattern worth noticing. Platform vendors are retiring old options on short notice, and the pipeline you never look at is where it breaks. Nothing in the notice affects teams building for modern 64-bit phones and servers.
So what
Ask your development partner one question this week: do any of our builds or tests run on ARM32 hosted runners, and if so, what is the plan for 8 December? The answer is usually to move to 64-bit targets, use self-hosted runners, or test on emulated or real devices instead. Our custom software development team audits build pipelines and device targets as part of any engagement. To have yours checked before the deadline, start a project.