From the setup-python source, the python-versions manifest, GitHub's runner-images pages and real runs, read 18 November 2026 · Updated
"The version '3.9' with architecture 'x64' was not found for Ubuntu 26.04": setup-python on ubuntu-latest, and the fix
Your workflow did not change; the runner did. GitHub is moving ubuntu-latest to Ubuntu 26.04 (a rollout planned from 19 October to 19 November 2026), and your job landed on it. actions/setup-python installs Python from a manifest of prebuilt builds, and that manifest has no Ubuntu 26.04 build of 3.8 or 3.9 at all. For 3.10 to 3.14 it has builds only from one patch release up (the "floor" in the table). If the version you asked for has no build for the runner's OS, the action stops with the error in the title. A bare minor such as '3.12' resolves to a build that exists; an exact pin such as '3.12.10' does not, because 26.04 starts at 3.12.13.
Find every setup step in your repo that fails on 26.04: paste your workflow into the 26.04 check.
What 26.04 has
Read from the actions/python-versions manifest on 18 November 2026: stable releases with a Linux x64 file for Ubuntu 26.04.
| Python | Lowest patch with a 26.04 build (the floor) | Highest patch with a 26.04 build |
|---|---|---|
| 3.8 | none | none |
| 3.9 | none | none |
| 3.10 | 3.10.20 | 3.10.22 |
| 3.11 | 3.11.15 | 3.11.18 |
| 3.12 | 3.12.13 | 3.12.16 |
| 3.13 | 3.13.13 | 3.13.18 |
| 3.14 | 3.14.6 | 3.14.10 |
| 3.15 | 3.15.0 | 3.15.2 |
The same manifest has Ubuntu 24.04 builds of 3.8 (up to 3.8.18) and 3.9 (up to 3.9.25). The manifest lists files per platform, so Windows and macOS runners are a separate read that this page did not make. Everything below was run on the runner images named in each result: ubuntu-26.04 was Ubuntu 26.04.1 LTS (image 20261111.196.1) and ubuntu-24.04 was Ubuntu 24.04.5 LTS (image 20261111.370.1).
What the error looks like
setup-python v7.1.0 builds the message from the version you asked for, the architecture, and the OS name and number, then adds a second line. This is the text from a real run of ours on ubuntu-latest on 16 November 2026, copied from the job annotation:
The version '3.9' with architecture 'x64' was not found for Ubuntu 26.04.
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.jsonThe first line carries whatever version you asked for: '3.8', '3.12.10', '3.11.9'. That run used setup-python@v5; the message code is the same text in v7.1.0, which is the version we read and ran for everything else here.
Fix 1: keep the job on Ubuntu 24.04
Change one line. Python 3.9 installed (3.9.25) on ubuntu-24.04; so did '3.12.10'.
runs-on: ubuntu-24.04
steps:
- uses: actions/setup-python@v7.1.0
with:
python-version: '3.9'GitHub's runner-images README says a -latest label can change OS version during a migration, and that naming a specific version in the workflow avoids that. Its rollout notice says the move to 26.04 begins 19 October 2026 and is planned to be complete by 19 November 2026. We found no retirement date for ubuntu-24.04 in that README or in the titles of issues in that repository (searched 18 November 2026), so this page gives none. Ubuntu's own release-cycle page lists standard security maintenance for 24.04 LTS until May 2029.
Fix 2: move to a version that has a 26.04 build
Use a bare minor, or an exact patch at or above the floor in the table. Both installed on ubuntu-26.04:
runs-on: ubuntu-26.04
steps:
- uses: actions/setup-python@v7.1.0
with:
python-version: '3.12''3.12' installed 3.12.16. This:
- uses: actions/setup-python@v7.1.0
with:
python-version: '3.12.13'installed 3.12.13. On the same runner, '3.12.10' failed. We ran that one minor only; the manifest shows the same shape for 3.10, 3.11, 3.13 and 3.14.
This changes the Python your tests run on, which can change results. Python's own status page lists 3.8 (end of life 7 October 2024), 3.9 (31 October 2025) and 3.10 (1 October 2026) as end-of-life.
Fix 3: you need 3.9 on 26.04
setup-python cannot install it there. uv can download a portable CPython 3.9 build. This ran on ubuntu-26.04 and printed Python 3.9.25:
runs-on: ubuntu-26.04
steps:
- uses: astral-sh/setup-uv@v10.3.3
- run: |
uv python install 3.9
uv venv -p 3.9
.venv/bin/python --versionThat installed uv 0.13.9. We ran 3.9 only, not 3.8. The build comes from uv's own downloads, not from GitHub's manifest. It is still Python 3.9, past end of life on Python's own page.
After a failed setup step, python is not what you pinned
On ubuntu-26.04 with a failed setup step (continue-on-error: true), the python on the PATH was the system one, Python 3.14.4. A job that carries on after the error runs your tests on 3.14.4.
The other legs show "cancelled"
With a matrix and the default fail-fast, one failed leg cancels the rest. In a run of ours on 16 November 2026, a matrix of 3.9, 3.11, 3.13 and 3.14 on ubuntu-latest had one failed leg (3.9) and three legs reported as cancelled. Two of those had passed setup, and one of the two (3.13) had also run its tests to success, so a leg marked cancelled can hide a pass.
To see the other legs finish, set fail-fast: false. Matrix of 3.9 and 3.12 on ubuntu-26.04: the 3.9 leg failed at setup and the 3.12 leg passed, printing Python 3.12.16.
runs-on: ubuntu-26.04
strategy:
fail-fast: false
matrix:
python-version: ['3.9', '3.12']
steps:
- uses: actions/setup-python@v7.1.0
with:
python-version: ${{ matrix.python-version }}
- run: python --version.python-version and pyproject.toml pins
setup-python reads a version from python-version-file: a .python-version file, a pyproject.toml (its project.requires-python), .tool-versions or Pipfile. All four are in its documentation; we ran two file types.
| File content | Result on ubuntu-26.04 |
|---|---|
.python-version containing 3.9.18 | Failed at setup. |
.python-version containing 3.12 | Passed, Python 3.12.16. |
pyproject.toml with requires-python = ">=3.9" | Passed, but the job ran Python 3.15.2. |
pyproject.toml with requires-python = "~=3.9.0" | Failed at setup. |
With >=3.9, setup-python installed 3.15.2, the newest stable 26.04 build in the manifest that day, which may be newer than anything your tests have run on. We did not run .tool-versions or Pipfile.
Check the rest of your repo
Sources and read times
All read on 18 November 2026 (UTC) unless marked.
actions/setup-pythonv7.1.0 (released 22 October 2026):src/(the message),find-python.ts src/(the manifest URL),install-python.ts src/andutils.ts docs/advanced-usage.md(python-version-file).actions/python-versionsversions-manifest.json, main.actions/runner-images: README (image labels,-latestmigration) and theubuntu-latestnotice for 26.04.- Ubuntu release cycle: ubuntu.com/
about/ .release-cycle - Python status of versions: devguide.python.org/
versions . astral-sh/setup-uvv10.3.3.- Real runs: a private test repository (runs 44269844653, 44270171615, 44270305020, 44271006924, 18 November 2026) and our own CI run of 16 November 2026, whose annotations are public.
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.