← All posts

GitHub Actions is retiring ARM32 runners on 8 December 2026

StackClock team ·

GitHub announced on 12 November 2026 that GitHub Actions hosted runners will end support for ARM32 job execution on both Linux and Windows by 8 December 2026. A workflow that still targets ARM32 will not be able to run on a hosted runner after that date.

If your pipeline builds or tests for 32-bit ARM, this is a deadline with a date on it, and it is close.

What is changing

According to GitHub's announcement:

  • Hosted runners end support for ARM32 job execution on Windows and Linux by 8 December 2026.
  • Native AArch32 user-space execution is removed from hosted runners.
  • The change follows the end of support for node20. Node 24 does not support ARM32, so the JavaScript runtime that actions run on can no longer be provided there.

The notice is about GitHub-hosted runners. It says nothing about self-hosted runners, so do not assume they are unaffected. Check GitHub's documentation and the community discussion linked from the announcement before you decide.

Who should check

You are most likely to be affected if you:

  • build firmware, embedded software or Raspberry Pi images for 32-bit ARM
  • run tests on a 32-bit ARM environment to catch architecture-specific bugs
  • publish binaries or container images for linux/arm/v7 or similar 32-bit ARM targets
  • use a reusable workflow or an action from someone else that runs jobs on ARM32

How to find the workflows that depend on it

  1. Search your repositories' .github/workflows folders for runner labels and matrix entries that mention arm, armv7, armhf or arm32.
  2. Search for container platform lists such as linux/arm/v7 in your build steps.
  3. Look at third-party actions and reusable workflows you call. They can run jobs on ARM32 without you ever writing the word.

What to do before 8 December

  • Move the job to a supported architecture. If you only need the result, not the 32-bit run itself, run it on a 64-bit runner.
  • Cross-compile. Build the 32-bit artefact on a 64-bit runner with a cross toolchain instead of running the build on ARM32.
  • Emulate for tests. If you must run 32-bit ARM binaries, QEMU user-mode emulation on a 64-bit runner is the usual fallback. It is slower, so expect longer jobs.
  • Use your own runner. If you need real 32-bit hardware, a self-hosted runner is an option once you have confirmed it is supported for your setup.

Whichever you pick, change it on a branch and run it well before the 8th, not on the day.

Keep track of vendor deadlines like this

This is the kind of change that arrives as a one-minute changelog entry and breaks a pipeline weeks later. We track it on our GitHub deprecations page with its date, and StackClock reminds you ahead of time when a vendor change matches something in your stack.

You can also run the free stack check to see which of your dependencies and runtimes have deadlines coming up.