GitHub Actions hosted runners will stop running ARM32 jobs on Linux and Windows on 8 December
GitHub announced on 12 November that its hosted runners for GitHub Actions will end support for ARM32 job execution on Linux and Windows by 8 December 2026. The changelog entry also says that native AArch32 user-space execution on hosted runners is being removed.
The reason given is a chain of dependencies rather than a policy choice. GitHub has already ended support for node20 in Actions, the runner and JavaScript actions now use Node 24, and Node 24 does not support ARM32. Without a Node runtime for the architecture, the runner itself cannot keep executing jobs there, so ARM32 has to go.
The notice is short and leaves details to a GitHub Community discussion linked from the post. What it does make clear is the date and the scope: hosted runners, Linux and Windows, ARM32 and AArch32 user space. Teams that build or test 32-bit ARM artefacts on GitHub's hosted machines have about three and a half weeks to move that work.
The practical options are familiar ones. Builds that only need to produce ARM32 binaries can usually cross-compile on 64-bit runners, or run under emulation with QEMU inside a container, at the cost of slower jobs. Projects that need to run tests on real 32-bit hardware, for instance libraries aimed at older Raspberry Pi models or industrial boards, will need self-hosted runners on that hardware. Any workflow that pins a runner label tied to ARM32 should be checked before the cut-off, since jobs that cannot find a runner simply sit queued and then fail.
The entry lands in a busy period for Actions changes. The same changelog lists pull_request_target being blocked by default from 2 December, the general availability of workflow lockfiles and agentic workflows in October, and the retirement of the macOS 14 runner image at the start of October.

Why it matters
ARM32 is not dead in the field: plenty of embedded and maker hardware still ships it. But hosted CI follows its toolchain, and once Node dropped the architecture, GitHub's hosted runners had little reason to keep it. Projects that support 32-bit ARM should check where their tests actually run before 8 December, not after the first failed release build.