GitHub announced on November 12, 2026 that its hosted runners for GitHub Actions will stop supporting 32-bit ARM (ARM32) job execution on both Linux and Windows. The cutoff date is December 8, 2026, which gives teams a little under four weeks to move affected workflows.
The retirement also removes support on hosted runners for running native AArch32 user-space code. GitHub ties the decision to the earlier end of Node 20 in Actions, since Node 24 does not support ARM32. Teams that still build or test 32-bit ARM software in CI should plan around it now.
What GitHub Is Retiring
The changelog entry is short, but it covers two related pieces. First, ARM32 jobs on hosted Linux and Windows runners lose support by December 8, 2026. Second, hosted runners will no longer offer native AArch32 user-space execution, the mode that lets 32-bit ARM programs run directly on a 64-bit ARM processor.
- Scope: GitHub-hosted runners on Linux and Windows.
- What goes away: ARM32 job execution and native AArch32 user-space execution.
- Deadline: December 8, 2026.
- Reason given: Node 24, which replaced Node 20 for JavaScript actions, has no ARM32 support.
GitHub points users to its Community discussions for questions. The entry is labeled as a retirement in the Actions section of the changelog.
Why Node 24 Drives the Change
On September 23, 2026, GitHub posted its final notice that Node 20 was gone from Actions runners. From that point, runners use Node 24 for every JavaScript action, and the temporary environment variable that let workflows keep using the old, insecure Node version stopped working.
That same notice already warned that Node 24 lacks official ARM32 support and does not work on macOS 13.4 or older. It said self-hosted runners on those systems or architectures were no longer supported on github.com and GitHub with Data Residency. The new announcement extends the same logic to hosted runners.
The link matters because the runner itself depends on Node to run JavaScript actions such as checkout, cache and setup steps. If the runtime cannot run on a 32-bit ARM environment, most real-world workflows would break there anyway. GitHub is now making the end of that path official.
Who Is Affected
Most developers will not notice anything. Typical workflows run on x64 or 64-bit ARM (arm64) runners, and those are not part of this retirement. The change mainly hits projects that target older or low-cost 32-bit ARM hardware.
- Embedded and IoT projects that build or test for ARMv7 boards.
- Open-source libraries that publish 32-bit ARM binaries, wheels or packages.
- Teams that run 32-bit ARM test suites directly on arm64 hosted runners using the AArch32 compatibility mode.
- Organizations that still keep self-hosted runners on 32-bit ARM devices, which already lost support with the Node 20 removal.
If none of your workflow files mention ARM32, armv7, armhf or a 32-bit ARM target, you are very likely unaffected.
What It Means for Developers
The practical risk is a CI pipeline that suddenly fails in December with little warning. A release job that builds a 32-bit ARM artifact could stop working right before a holiday freeze. Checking now is cheaper than debugging a broken release later.
Start by searching your repositories for workflow files that mention 32-bit ARM targets or run 32-bit binaries on arm64 runners. Pay special attention to build matrices, since an ARM32 entry can hide among many other platform combinations. Release and packaging workflows deserve the closest look.
Next, decide whether you still need ARM32 at all. Many projects carry 32-bit ARM targets out of habit, while their users moved to 64-bit hardware long ago. Dropping the target may be the simplest fix, but tell your users first if you publish binaries for them.
If you must keep shipping 32-bit ARM builds, consider cross-compiling on a supported 64-bit runner, or testing through CPU emulation such as QEMU inside a container. These are common community approaches rather than something GitHub prescribes in the notice, so test them on your own pipeline well before the deadline.
How to Prepare Before December 8
A short checklist can help teams finish the work in time. The steps below assume you control the workflow files in your repositories.
- List every workflow and matrix entry that targets ARM32 or runs 32-bit ARM code.
- Confirm all JavaScript actions you use declare Node 24, since Node 20 actions no longer run.
- Move 32-bit ARM builds to cross-compilation or emulation on a supported runner, or remove them.
- Retire or upgrade any self-hosted runner still running on a 32-bit ARM device.
- Run the updated workflows once before the cutoff to catch surprises early.
Recent changes such as workflow lockfiles reaching general availability and pull_request_target being blocked by default from December 2 also land around the same time. It makes sense to review all of them in one pass of your workflow files.
Conclusion
GitHub is closing the door on 32-bit ARM in Actions. Hosted runners on Linux and Windows lose ARM32 job execution and native AArch32 user-space support on December 8, 2026, following the switch to Node 24, which never supported the architecture.
Most teams will be untouched, but projects that still ship or test 32-bit ARM code should audit their workflows now. Cross-compiling, emulating or dropping the target are the realistic options, and each one is easier to try before the deadline than after it.
Sources
- GitHub Changelog: Actions for ARM32 Linux & Windows retirement
- GitHub Changelog: Node 20 is no longer available in GitHub Actions
See my articles more often when you search Google.
