GitHub Actions ends ARM32 runner support on 8 December 2026

GitHub is retiring ARM32 job execution on its hosted Actions runners for Linux and Windows by 8 December 2026. Teams that build or test for older ARM32 devices need a plan for their CI pipelines.

On 12 November 2026 GitHub posted a retirement notice: hosted GitHub Actions runners will stop supporting ARM32 job execution on both Windows and Linux by 8 December 2026.

What GitHub says

Why a non-developer should care

ARM32 is the older 32-bit chip design. Most current phones and laptops have moved on, but it still sits inside industrial equipment, kiosks, older Android hardware and embedded devices. If your product has to run on any of those, the automated build and test pipeline behind it may depend on exactly the runners GitHub is switching off.

This is also a pattern worth noticing. Platform vendors are retiring old options on short notice, and the pipeline you never look at is where it breaks. Nothing in the notice affects teams building for modern 64-bit phones and servers.

So what

Ask your development partner one question this week: do any of our builds or tests run on ARM32 hosted runners, and if so, what is the plan for 8 December? The answer is usually to move to 64-bit targets, use self-hosted runners, or test on emulated or real devices instead. Our custom software development team audits build pipelines and device targets as part of any engagement. To have yours checked before the deadline, start a project.

← All research

More research.

GitHub Copilot adds Supabase, Webflow, Wix and five more connectors in public preview

GitHub Copilot now connects to eight more services, including Supabase, Webflow, Wix and Mixpanel, through verified MCP connectors in public preview. They join more than 25 existing ones.

Read ›

Gemini 4 Neon is generally available in GitHub Copilot, aimed at lower-cost agentic coding

Gemini 4 Neon is now generally available in GitHub Copilot for agentic coding. Google says its quality is close to Gemini 4 Carbon at a lower token cost per task.

Read ›

Claude Code 2.1.328 brings auto mode to Bedrock, Vertex and Foundry, and narrows /code-review to bugs

Claude Code 2.1.328 extends auto mode to Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud and Microsoft Foundry. /code-review now reports only bugs and CLAUDE.md violations.

Read ›

GitHub Copilot Evals: repeatable tests for AI agents, now in public preview

GitHub Copilot Evals lets teams write repeatable tests for AI coding skills, custom agents and MCP tools. It checks both the result and the path the agent took, and is in public preview.

Read ›

GitHub Copilot can now drive your browser: browser use enters public preview

GitHub Copilot browser use lets an AI coding agent control Chrome to debug web apps and run browser tests. It is in public preview across the CLI, the Copilot app, VS Code and JetBrains.

Read ›

Claude Code 2.1.327 refuses some symbolic links and lists broken setup in /status

Claude Code 2.1.327 tightens file and package permissions again and adds a /status list of broken agent, skill and hook settings. A short read for teams using AI coding tools on a live product.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work