Original announcement: GitHub · 2026-11-12. Read the official announcement.
Summary
On November 12, 2026, GitHub announced that its Actions platform will retire support for running jobs on ARM32 architecture runners for both Linux and Windows operating systems. This change is set to take effect by December 8, 2026, and aligns with the broader discontinuation of Node.js 20 support, as its successor Node.js 24 no longer supports ARM32 architectures. The retirement includes the removal of native AArch32 user-space execution on hosted runners.
What Happened?
- GitHub Actions hosted runners will stop supporting job execution on ARM32 (AArch32) architectures for Linux and Windows by December 8, 2026.
- This decision follows GitHub’s end of support for Node.js 20 because Node.js 24 lacks ARM32 support.
- Hosted runners will no longer support native AArch32 user-space execution on the affected OSs.
- Developers can join discussions in the GitHub Community regarding this change.
Who Should Care?
This update primarily affects developers and organizations currently relying on GitHub Actions workflows that run on ARM32 Linux or Windows hosted runners. Projects dependent on ARM32-based environments for builds, tests, or deployment tasks must plan for this upcoming deprecation to avoid workflow failures.
What Should Developers Do Next?
- Assess ARM32 Dependency: Identify if your GitHub Actions workflows run jobs on ARM32 Linux or Windows hosted runners.
- Alternative Architectures: Consider migrating workflows to supported runner architectures such as ARM64 or x86_64.
- Update Tooling: Verify compatibility of your build tools and dependencies with architectures supported by GitHub Actions post-December 2026.
- Community Engagement: Participate in GitHub Community discussions to stay informed and provide feedback.
Practical Checklist
- Inventory current workflows to detect ARM32 usage on Linux and Windows runners.
- Test workflows on alternative supported architectures to ensure compatibility.
- Plan migration timelines ahead of the December 8, 2026 deadline.
- Monitor GitHub announcements and community feedback for any updates.
