GitHub has set December 8, 2026 as the end date for ARM32 job execution on GitHub-hosted Linux and Windows runners. Its November 12 changelog says the change follows the end of Node 20 support because Node 24 does not support ARM32. It also says hosted runners will remove native AArch32 user-space execution. This affects workflows that rely on hosted ARM32 execution; it is not a general shutdown of GitHub Actions.
Which workflows should teams check?
Start with workflow files and the runner configuration for every job. Look for an ARM32-specific hosted image or a job that expects native 32-bit ARM user space, then check its build scripts, action versions and compiled dependencies. The architecture can be hidden inside a reusable workflow or an action, so search across the repository and review recent logs from jobs that actually run on the target architecture. A green x64 build does not show that an ARM32-specific test is still covered.
The date matters for projects that release or validate ARM32 software: after December 8, a hosted job cannot rely on native ARM32 user-space execution in Linux or Windows. A workflow that only runs on x64 or ARM64 is outside this specific retirement, though it may still need its own dependency and compatibility checks.
What are the alternatives?
If the job does not specifically need 32-bit ARM, move it to a hosted architecture the current GitHub runner documentation lists, such as x64 or ARM64, and validate the project's dependencies on that architecture. GitHub documents ARM64 hosted labels for Linux and Windows; available labels and plan eligibility should be checked in the current runner reference before changing a workflow.
If testing on 32-bit ARM is essential, GitHub's current self-hosted runner reference lists ARM32 support for Linux. That leaves a path for a team to operate its own Linux ARM32 runner, but it moves machine maintenance, network access, isolation and availability to the team. The reference does not list ARM32 for self-hosted Windows. Do not treat a Linux ARM32 runner as a drop-in Windows replacement: keep tests matched to the operating system and hardware behavior they are meant to validate.
GitHub retirement notice: December 8 deadline and affected hosted execution
GitHub-hosted runner reference: current operating systems and architecture labels
Self-hosted runner reference: ARM32 Linux support and other architectures
Make the migration test the right thing
Changing `runs-on` can restore a scheduled job, but it may also change the environment the software is being tested in. Review which architecture and operating system the release truly supports, update any incompatible build dependencies, and keep an explicit ARM32 test if that remains a release requirement. For teams using hardware or device-specific test rigs, GitHub's notice is a deadline to check the whole path from workflow configuration to test environment, not just a YAML label.
The retirement is less than a month away from this announcement. Teams that rely on native ARM32 hosted jobs should inventory them now, choose a supported hosted architecture or an appropriate self-hosted Linux ARM32 runner, and run the affected workflow before the deadline.