You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: The version '3.8' with architecture 'x64' was not found for Ubuntu 24.04.
or
Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 22.04.
Hello @Flamefire👋,
Thank you for reporting this issue and providing the detailed context and logs.
We have attempted to reproduce the problem on our end, but we were successfully able to install Python versions 3.7 and 3.8 on the specified Ubuntu runners using the same action version as your workflow. Everything appears to be working as expected at this time.
There may have been a temporary outage causing the failure. Could you please try rerunning your workflow to see if the issue persists? Thank you!
Yes looks like a temporary issue. Maybe the error reporting can be improved as the error isn't that the versions didn't exist but either that downloading the list or files failed or some parsing failed.
An idea: Instead of showing basically "version x not available here, look in this file", the error could list all available version in the current runner/OS and the OSes where the requested version is available so one can easily change either without search through a file that is meant to be machine readable (only). What do you think about that?
The fix from PR #1332 has been merged into the main branch. The update improves handling of invalid or truncated versions-manifest.json responses by validating the manifest, retrying failed fetches with backoff, and reporting a clear failure if all retry attempts are exhausted.. The changes are available in actions/setup-python@main and will be included in an upcoming release.
Regarding your suggestion to list all available versions in the error message- Thank you for the thoughtful idea! Unfortunately, the full set of versions across every supported runner/OS is quite large, and printing it inline would make the logs noisy and harder to read. For that reason, we point to the manifest, which stays complete and always up to date:
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
That said, the recent fix should reduce these errors, since transient manifest-fetch failures are now retried and reported clearly. We'll go ahead and close this issue. Please feel free to reach out if you run into any further problems. Thank you for your patience!
Activity
v-priya-kinthali commentedon May 29, 2026
Hello @Flamefire👋,
Thank you for reporting this issue and providing the detailed context and logs.
We have attempted to reproduce the problem on our end, but we were successfully able to install Python versions 3.7 and 3.8 on the specified Ubuntu runners using the same action version as your workflow. Everything appears to be working as expected at this time.
There may have been a temporary outage causing the failure. Could you please try rerunning your workflow to see if the issue persists? Thank you!
Flamefire commentedon May 29, 2026
Yes looks like a temporary issue. Maybe the error reporting can be improved as the error isn't that the versions didn't exist but either that downloading the list or files failed or some parsing failed.
An idea: Instead of showing basically "version x not available here, look in this file", the error could list all available version in the current runner/OS and the OSes where the requested version is available so one can easily change either without search through a file that is meant to be machine readable (only). What do you think about that?
v-priya-kinthali commentedon Jul 16, 2026
Hi @Flamefire,
The fix from PR #1332 has been merged into the main branch. The update improves handling of invalid or truncated versions-manifest.json responses by validating the manifest, retrying failed fetches with backoff, and reporting a clear failure if all retry attempts are exhausted.. The changes are available in
actions/setup-python@mainand will be included in an upcoming release.Regarding your suggestion to list all available versions in the error message- Thank you for the thoughtful idea! Unfortunately, the full set of versions across every supported runner/OS is quite large, and printing it inline would make the logs noisy and harder to read. For that reason, we point to the manifest, which stays complete and always up to date:
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
That said, the recent fix should reduce these errors, since transient manifest-fetch failures are now retried and reported clearly. We'll go ahead and close this issue. Please feel free to reach out if you run into any further problems. Thank you for your patience!