ARM32 runner support removed from GitHub Actions hosted Windows and Linux

GitHub Actions announced that, as of 8 December 2026, its hosted runners will no longer support ARM32 job execution on both Windows and Linux platforms. The change follows the earlier retirement of node20, noting that the upcoming node24 runtime does not include ARM32 binaries. Practitioners who rely on AArch32 user‑space execution in CI pipelines need to plan for migration.

What Changed

The hosted runner environment will drop native ARM32 (AArch32) support entirely. This removal applies to all Windows and Linux runner images provided by GitHub and is tied to the lack of ARM32 compatibility in the next Node.js version.

Impact on Architecture and Implementation

• CI jobs targeting ARM32 must be retargeted to a supported architecture such as ARM64 or x86_64.
• Build scripts that depend on node20 features will need to be updated to run on node24 or an alternative runtime that aligns with the new architecture.
• Projects that cannot shift to a different architecture will need to consider self‑hosted runners that still run on ARM32 hardware.

Operational Considerations

Teams should audit existing workflows for ARM32 usage before the deprecation date. Monitoring for failed jobs after the cutoff will help surface pipelines that were missed. If self‑hosted runners are chosen, operational responsibilities such as patching, security hardening, and capacity planning shift back to the organization.

Related CloudNinjas coverage: DevOps.

What This Means For Practitioners

Evaluate all GitHub Actions workflows for ARM32 dependencies and create a migration plan that either updates the target architecture or provisions self‑hosted runners. Track GitHub communications for any further guidance and test the revised pipelines well before the 8 December deadline to avoid unexpected CI breakage.