GitHub begins ubuntu-latest migration to Ubuntu 26.04
The staged rollout runs through November 19 and may send identical workflows to different images; test or temporarily pin the runner.
R42 / SUMMARY
GitHub began the gradual migration of the x64 ubuntu-latest runner from Ubuntu 24.04 to 26.04 on October 19, 2026. The rollout ends November 19 and may affect pipelines that depend on image-specific tools or versions. GitHub recommends testing ubuntu-26.04 or temporarily pinning ubuntu-24.04.
KEY POINTS
- The staged migration runs from October 19 to November 19, 2026.
- Workflows using ubuntu-latest will move automatically to Ubuntu 26.04.
- Preinstalled dependencies, system libraries and specific binaries may cause failures.
- GitHub recommends testing ubuntu-26.04 or temporarily pinning ubuntu-24.04.
GitHub began the gradual migration of the ubuntu-latest label in GitHub Actions on Monday, October 19, 2026. The label is moving from Ubuntu 24.04 to Ubuntu 26.04, with completion planned for November 19. The change is automatic for workflows using the standard GitHub-hosted x64 runner.
The most important consequence of the staged schedule is that the switch does not happen for every repository at once. For roughly a month, two projects with the same runs-on: ubuntu-latest setting may run on different images. A workflow may also pass on one run and encounter Ubuntu 26.04 on a later run as the rollout progresses.
What may break during the migration
GitHub warns that builds depending on preinstalled packages, system libraries, compilers, binaries or specific versions may fail. That does not mean every pipeline must be changed. Workflows that explicitly install and pin their own versions generally depend less on the variable contents of the hosted image. The most exposed jobs are those that silently assume a tool available on the runner will remain installed and behave the same way.
Confirmed image differences include the move from Ubuntu 24.04.5 LTS to Ubuntu 26.04.1 LTS, Linux kernel 6.17 to 7.0 and systemd 255 to 259. Other tools retain the same listed version across both images, including Docker Buildx, Minikube, AWS CLI, Azure CLI, Google Cloud CLI, Rust, Firefox and GitHub’s listed default Java version. The practical implication is that teams should investigate each dependency instead of assuming that every component changed in the same way.
GitHub’s official recommendation is to test with runs-on: ubuntu-26.04. Teams that are not ready to migrate can temporarily set ubuntu-24.04. Pinning the older image prevents an unexpected switch during the rollout, but it does not replace an upgrade plan; it only makes the environment predictable while tests and dependencies are updated.
The change does not upgrade computers or servers
The migration affects the hosted image used by GitHub Actions jobs. It does not automatically upgrade Ubuntu on developer workstations, private servers or self-hosted runners. Ubuntu 26.04 is an LTS release issued in April 2026 and, according to Canonical, will receive security updates and critical bug fixes for five years, through April 2031.
GitHub also provides explicit x64 and Arm64 images through the ubuntu-26.04 and ubuntu-26.04-arm labels. The announced ubuntu-latest transition specifically concerns the standard x64 label. Projects using architecture matrices should therefore inspect each entry separately rather than assuming there is one universal switch.
How to reduce uncertainty without freezing CI
A minimum audit starts by locating every job that uses ubuntu-latest, including values generated by matrices and reusable workflows. Teams should then identify tools used without a setup action or pinned version. Running tests on Ubuntu 24.04 and 26.04 side by side helps separate failures caused by the new image from problems already present in the project.
The migration illustrates the tradeoff between convenience and reproducibility. The latest label reduces routine maintenance but lets the provider decide when the environment changes. An explicit version offers immediate stability while creating a responsibility to follow the support lifecycle. Either approach can be reasonable, but allowing the rollout to proceed without testing is effectively accepting an infrastructure upgrade without a dedicated validation window.
R42 / SOURCES CONSULTED
References used to verify facts and provide context for this story.
-
Ubuntu 26.04 LTS release notes
Canonical
-
[Ubuntu] ubuntu-latest label will use Ubuntu 26.04 in November 2026
GitHub Actions runner-images
Gabriel Silva
Credited author of this story. Visit the profile for other publications.
R42 / FAQ
When does ubuntu-latest move to Ubuntu 26.04?
The migration began on October 19, 2026, and will be completed gradually by November 19, 2026.
Do I need to change every GitHub Actions workflow?
Not necessarily. The ubuntu-latest label will update automatically, but pipelines that depend on specific image tools, libraries or versions should be tested on Ubuntu 26.04.
How can I stay on Ubuntu 24.04 during the transition?
Temporarily set runs-on to ubuntu-24.04. This keeps the environment stable while your team tests and fixes compatibility issues.
Does the migration upgrade my server or computer?
No. It only changes GitHub-hosted Actions runner images; local machines, private servers and self-hosted runners are not upgraded.