PuppyIP Resource Center
Developer Tool Updates 4 min Published 2026-11-14

GitHub Actions ARM32 Hosted Job Support Ends by December 8, 2026

By December 8, 2026, GitHub will end ARM32 job support on its hosted Linux and Windows runners. A runner is the machine that executes automation jobs; the change includes native AArch32 user-space execution, or directly running 32-bit ARM user programs. First inventory your workflows’ actual execution architecture, then check their actions for Node 24 compatibility. GitHub has not specified an exact cutover time or time zone.

GitHub Actions ARM32 AArch32 Node 24

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • By December 8, 2026, GitHub-hosted Windows and Linux runners will end ARM32 job execution support, including native AArch32 user-space execution.
  • The September 23 notice already said JavaScript actions use Node 24 and the temporary opt-out is gone. The November announcement adds a deadline for ARM32 execution in hosted environments.
  • Action maintainers update runs.using and publish a compatible release; workflow users select action versions that support Node 24.
  • ARM64 is distinct from ARM32, and the notice does not retire all 32-bit build artifacts. December 8 is not an extra grace period for self-hosted runners.

December 8: the GitHub-hosted ARM32 job deadline

On November 12, 2026, GitHub announced that GitHub-hosted runners will end ARM32 job execution support on Windows and Linux by December 8, 2026. This includes native AArch32 user-space execution. Prioritize workflows that need to run 32-bit ARM user programs directly on the runner.

The restriction concerns how jobs execute; it does not announce retirement of every 32-bit build artifact. ARM64 is a separate architecture, and the ARM32 notice does not establish an ARM64 retirement. Determine impact from the job’s actual execution method. GitHub gave no exact cutover hour or time zone.

Node 20 retirement was an earlier runtime change

GitHub’s September 23 notice already said Node 20 was no longer available on Actions runners and JavaScript actions now use Node 24. The temporary ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION opt-out was also removed. This is the runtime background to the architecture change; the old switch cannot be relied on to retain Node 20.

Node 24 does not officially support ARM32, so updating an action’s runtime declaration does not keep hosted ARM32 jobs supported. Check two things separately: whether the action is compatible with Node 24, and whether the job still depends on the execution architecture whose support is ending.

Choose the next step for your role

If you maintain a JavaScript action, the September notice says to change runs.using to node24 and publish a new release. If your workflow uses someone else’s action, select a compatible release that supports Node 24. A workflow is the automation configuration that defines jobs and steps in a repository. Maintainers publish releases; workflow owners choose which release to use.

Neither notice guarantees that a particular action, runner, or migration combination fits every project. Check the versions your repository actually references and their compatibility information, then plan validation. Changing only a runtime or runner label does not establish a successful migration.

Keep the self-hosted boundary separate and plan the migration

The September 23 Node 20 notice separately says self-hosted runners using ARM32 or macOS 13.4 and earlier are no longer supported. That statement applies to github.com and GitHub with Data Residency. It is a self-hosted runtime boundary from the Node 20/Node 24 change, not a December 8 grace period for self-hosted environments; the source does not establish the same change for GHES.

Before migrating, record whether each workflow uses GitHub-hosted or self-hosted runners, its operating system, actual architecture, and action runtimes and versions. List jobs that depend on ARM32 execution separately and leave time for compatibility checks before the date boundary. Maintainers still need to verify in their own projects that the replacement environment accepts jobs, completes the important steps, and produces the required results.

Sources

Frequently Asked Questions

Does changing the runner label to ARM64 complete the migration?

No. ARM64 is a different architecture, but the notice provides no universal replacement label or compatibility guarantee. Check the target environment, dependencies, and action versions, then verify execution and artifacts with representative jobs. A label change alone is not proof of success.

What if the latest version of an action does not support Node 24?

The Node 20 notice tells workflow users to choose action versions that support Node 24, but it does not name a compatible release for every action. Check the action’s own release information and ask its maintainer if no suitable version is available. Do not guess a version or use the removed Node 20 opt-out.