GitHub Actions changes: Node 24, Ubuntu 26.04 and runner updates that can break your CI/CD

If your team builds, tests or deploys with GitHub Actions, September 2026 brought three changes worth checking: Node 20 was removed in favor of Node 24, the ubuntu-latest label is moving to Ubuntu 26.04, and minimum versions for self-hosted runners are now enforced on GitHub Enterprise Cloud. None of them is dramatic on its own, but each can make a pipeline fail when nobody expects it.

Here is what changed, based on GitHub’s official changelog, and a checklist to keep your CI/CD running.

Timeline of the changes

Node 20 is gone: runners now use Node 24

On 23 September 2026, GitHub confirmed that Node 20 is no longer available on GitHub Actions runners, and that runners now use Node 24 for JavaScript actions. The temporary opt-out that allowed the old version is no longer available.

• If you maintain a JavaScript action, update its runs.using value to node24 and publish a new release.
• If you use JavaScript actions, update to the latest versions that support Node 24. GitHub’s own first-party actions have already been updated.
• Older systems are affected too. Node 24 is incompatible with macOS 13.4 and earlier and does not officially support ARM32, so self-hosted runners on those systems are no longer supported.

ubuntu-latest moves to Ubuntu 26.04

The Ubuntu 26.04 runner image became generally available on 17 September 2026 for x64 and arm64. The ubuntu-latest label will migrate from Ubuntu 24.04 to Ubuntu 26.04 gradually between 19 October and 19 November 2026. GitHub warns that the new image includes updated, and in some cases removed, tools, which can break workflows that depend on specific versions or preinstalled packages.

• Test your workflows with runs-on: ubuntu-26.04 (or ubuntu-26.04-arm) before the migration starts.
• If you are not ready, pin your workflows to ubuntu-24.04 to stay on the current image.

Minimum versions for self-hosted runners

On GitHub Enterprise Cloud, full enforcement of minimum versions for self-hosted runners began on 29 September 2026. Runners below version 2.329.0 cannot register or re-register, and existing runners below the minimum version required to run jobs will stop running jobs. GitHub Enterprise Server is not affected, and enforcement for GitHub Enterprise Cloud with Data Residency already began on 31 July 2026.

CI/CD checklist

1. 1Update your JavaScript actions to versions that support Node 24.
2. 2Set runs.using to node24 in any action you maintain, and publish a new release.
3. 3Run your workflows on ubuntu-26.04 now, before ubuntu-latest switches.
4. 4Pin ubuntu-24.04 for workflows that need more time.
5. 5Upgrade self-hosted runners to a supported version.
6. 6Retire runners on macOS 13.4 or earlier and ARM32, which Node 24 no longer supports.

What it means for your business

A pipeline that fails silently delays every release: new features, bug fixes and security patches all wait. The migration window for ubuntu-latest is gradual, which means a workflow can pass one day and fail the next without any code change. That is exactly the kind of issue that costs a team hours to diagnose if nobody is watching the changelog.

Keeping your pipeline current is part of keeping your product secure. For example, the Next.js security release this month can only be deployed quickly if your CI/CD is healthy.

How Estontinc can help

We audit and maintain GitHub Actions pipelines: updating actions and runners, testing on new images and documenting the setup so your team knows how releases work. See our cloud & DevOps service, and our custom software and web development teams for the applications behind the pipeline.

Want a second pair of eyes on your pipeline? Tell us about your setup and we will reply within 24 hours.