--- title: Actions for ARM32 Linux & Windows retirement | daily.dev description: GitHub Actions hosted runners will stop supporting ARM32 job execution on Windows and Linux by December 8, 2026. This follows the end of support for Node 20 in... canonical: https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Actions for ARM32 Linux & Windows retirement | daily.dev og:description: GitHub Actions hosted runners will stop supporting ARM32 job execution on Windows and Linux by December 8, 2026. This follows the end of support for Node 20 in... og:url: https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1 og:image: https://api.daily.dev/og/posts/1gNQFp9K1.png og:image:alt: Actions for ARM32 Linux & Windows retirement og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Actions for ARM32 Linux & Windows retirement **[GitHub Changelog](https://daily.dev/sources/github_updates)** · 1 min read · 0 upvotes · 1 comments ## Summary GitHub Actions hosted runners will stop supporting ARM32 job execution on Windows and Linux by December 8, 2026. This follows the end of support for Node 20 in Actions, where Node 24 does not support ARM32. Native AArch32 User-space execution support on hosted runners will also be removed. Users can join the discussion within GitHub Community. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### When does GitHub Actions stop supporting ARM32 on hosted runners? GitHub Actions hosted runners will end support for ARM32 job execution on Windows and Linux by December 8, 2026. This includes removal of native AArch32 User-space execution support. The change follows the earlier end of support for Node 20 in Actions, since Node 24 does not support ARM32. _Teams relying on ARM32 runners can track infrastructure deprecations like this on daily.dev before pipelines break._ ### Why is GitHub Actions removing ARM32 runner support? GitHub Actions is removing ARM32 support because Node 24, the runtime now used after Node 20 support ended in Actions, does not support ARM32. This makes continued ARM32 job execution on hosted runners incompatible with the required Node version. _Anyone planning CI migrations off ARM32 can follow runtime compatibility changes like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@sunnatulla\_dev** · 0 upvotes > The part people with a Raspberry Pi runner will miss: this isn't just hosted runners. I pulled the linux-arm tarball of the current self-hosted runner (v2.338.2) and it only ships externals/node20, a 32-bit ARM build. There is no node24 in it, and the worker quietly runs node24 actions on Node 20 with a warning. > > In the runner source the switch is a server-side flag, actions_runner_kill_linux_arm32 (NodeUtil.CheckNodeVersionForLinuxArm32). Once GitHub flips it, every JS action step fails with "Linux ARM32 runners are no longer supported", so actions/checkout and setup-node die, while plain... ## Similar posts on daily.dev - [GitHub Actions: Upcoming image migrations](https://daily.dev/posts/github-actions-upcoming-image-migrations-mmerwdhnd) · GitHub Changelog · 0 upvotes · 0 comments - [Node 20 is no longer available in GitHub Actions](https://daily.dev/posts/node-20-is-no-longer-available-in-github-actions-9ufpapdh7) · GitHub Changelog · 3 upvotes · 2 comments - [Node 20 GitHub Actions Deprecated: Workflow Migration Guide](https://daily.dev/posts/node-20-github-actions-deprecated-workflow-migration-guide-mzgd7stse) · SitePoint · 0 upvotes · 0 comments - [arm64 standard runners are now available in private repositories](https://daily.dev/posts/arm64-standard-runners-are-now-available-in-private-repositories-txgrccvew) · GitHub Changelog · 0 upvotes · 0 comments - [August 14, 2026](https://daily.dev/posts/august-14-2026-ygs9ndaps) · The Old New Thing · 0 upvotes · 0 comments --- Tags: [#nodejs](https://daily.dev/tags/nodejs), [#cicd](https://daily.dev/tags/cicd), [#github-actions](https://daily.dev/tags/github-actions) [View this post on daily.dev](https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Actions for ARM32 Linux \u0026 Windows retirement","url":"https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1"},"datePublished":"2026-11-12T21:05:04.044Z","dateModified":"2026-11-13T14:35:54.713Z","description":"GitHub Actions hosted runners will stop supporting ARM32 job execution on Windows and Linux by December 8, 2026. This follows the end of support for Node 20 in...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/34f4a8b6a99dc2bd1aca6124143d4bcf?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/34f4a8b6a99dc2bd1aca6124143d4bcf?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"nodejs,cicd,github-actions","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Actions for ARM32 Linux \u0026 Windows retirement"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1","comment":[{"@type":"Comment","text":"The part people with a Raspberry Pi runner will miss: this isn’t just hosted runners. I pulled the linux-arm tarball of the current self-hosted runner (v2.338.2) and it only ships externals/node20, a 32-bit ARM build. There is no node24 in it, and the worker quietly runs node24 actions on Node 20 with a warning.\nIn the runner source the switch is a server-side flag, actions_runner_kill_linux_arm32 (NodeUtil.CheckNodeVersionForLinuxArm32). Once GitHub flips it, every JS action step fails with “Linux ARM32 runners are no longer supported”, so actions/checkout and setup-node die, while plain run: steps still work. Updating the runner won’t help.\nQuick check on a Pi: file ~/actions-runner/externals/node20/bin/node. If it says “ELF 32-bit … ARM” you’re on the arm build, even with a 64-bit kernel. Pi 3/4/5 can take 64-bit Raspberry Pi OS and the arm64 runner, which has node24.","datePublished":"2026-11-13T13:18:55.589Z","url":"https://daily.dev/posts/1gNQFp9K1#c-Z9JFrjWBZ","author":{"@type":"Person","name":"Sunnatulla E.","url":"https://daily.dev/sunnatulla_dev","image":"https://lh3.googleusercontent.com/a/ACg8ocJo-F7wmmAt8NSb8q7sICb2AcjYKKjZ4SLvvn97P34Ovt-DjA=s96-c"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/actions-for-arm32-linux-windows-retirement-1gnqfp9k1#faq","mainEntity":[{"@type":"Question","name":"When does GitHub Actions stop supporting ARM32 on hosted runners?","acceptedAnswer":{"@type":"Answer","text":"GitHub Actions hosted runners will end support for ARM32 job execution on Windows and Linux by December 8, 2026. This includes removal of native AArch32 User-space execution support. The change follows the earlier end of support for Node 20 in Actions, since Node 24 does not support ARM32. Teams relying on ARM32 runners can track infrastructure deprecations like this on daily.dev before pipelines break."}},{"@type":"Question","name":"Why is GitHub Actions removing ARM32 runner support?","acceptedAnswer":{"@type":"Answer","text":"GitHub Actions is removing ARM32 support because Node 24, the runtime now used after Node 20 support ended in Actions, does not support ARM32. This makes continued ARM32 job execution on hosted runners incompatible with the required Node version. Anyone planning CI migrations off ARM32 can follow runtime compatibility changes like this on daily.dev."}}]} ```