arm64 standard runners are now available in private repositories

[samus-aran]

Starting today, Linux and Windows arm64 standard GitHub-hosted are now supported in private repositories. You can now use these free-tier eligible arm64 runners in all repositories, letting you take advantage of the performance benefits of arm64 processors and run native multi-architecture builds without the overhead of virtualization or emulation.

Because these are standard GitHub-hosted runners, usage counts towards the free minutes included in your plan.

What’s new

• Linux and Windows arm64 standard hosted runners are now supported in all repositories.
• In private repositories, these runners have 2 vCPUs; in public repositories, they have 4 vCPUs.
• These runners use an arm64 processor and images managed by Arm, LLC.

As standard GitHub-hosted runners, they are eligible for use towards your GitHub plan's free minute allocation in private repositories. macOS arm64 standard runners are already available for private repositories; this update extends private repository arm64 support to Linux and Windows.

This is ideal for teams targeting arm64 production - such as containerized services or multi-architecture builds - who want native performance using standard GitHub-hosted runners in private repositories.

Get started

To start building on arm64, add one of the following supported labels to the runs-on field in your workflow:

• windows-11-arm
• ubuntu-24.04-arm
• ubuntu-22.04-arm

For more details on arm64 runners and usage, see our documentation for standard GitHub-hosted runners. These runners are fully supported standard GitHub-hosted runners and are suitable for production CI workloads.

We would love to hear how much these now benefit your private projects!

Read more on our GitHub changelog

[ferferga]

Is there a plan to add a ubuntu-arm-latest tag similar to ubuntu-latest?

The 2nd most voted feature request from here: https://github.com/orgs/community/discussions/148648?sort=top#discussioncomment-11858187

Please do it next

[nebuk89]

@ferferga hmm apologies I had missed that this got so much engagement where it was threaded. Is there a dedicated community request for this? If not open one and we can track it onto the backlog <3

It's solid feedback and honestly I had just missed the demand was so high - thank you for bringing it back up!

[samus-aran]

Hey there I want to make sure we have capturing this feedback and having a dedicated discussion tracking it.

@junaruga did create a duplicate discussion here so I'll re-open that and guide folks to there so we can more easily track the demand 📈 🙌 Let me know if we need to update the request 👍

[junaruga]

@samus-aran Okay. Thanks for that.

[ferferga]

You guys were faster than me!
Upvoted the discussion

[jay0lee]

Sadly the Python cryptography library just dropped Windows arm64 wheel support specifically because the partner image is broken and problematic. Hopefully there's work underway to get this image updated and closely aligned with other runners:

pyca/cryptography#14216

[nebuk89]

Yep aware of the python issue - give us a bit <3