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
Description:
Add pre-compiled Python binaries for Debian (12 and 13) to the versions-manifest.json. Currently the manifest only includes Ubuntu (16.04–24.04), causing actions/setup-python to fail on Debian-based self-hosted runners with:
Error: The version '3.x' with architecture 'x64' was not found for Debian 13.
Requested additions:
Distro
Version
Architectures
Debian
12 (Bookworm)
x64, arm64
Debian
13 (Trixie)
x64, arm64
Justification:
Debian is one of the most widely deployed Linux distributions for self-hosted CI runners and server infrastructure. Ubuntu itself is derived from Debian and shares the same glibc/libc6 ABI, meaning the same build pipeline used to produce Ubuntu binaries should work for Debian with minimal changes. Without manifest entries for Debian, setup-python performs a platform detection check via /etc/os-release, finds no matching entry, and errors out — even though an Ubuntu 24.04 binary would run correctly on Debian 13. Users are forced to either switch their runner OS to Ubuntu or remove setup-python entirely and rely on the system Python, both of which are unnecessary workarounds given the binary compatibility.
Are you willing to submit a PR?
Yes, open to contributing if the maintainers can provide guidance on the build matrix configuration for Debian targets.
Description:
Add pre-compiled Python binaries for Debian (12 and 13) to the
versions-manifest.json. Currently the manifest only includes Ubuntu (16.04–24.04), causingactions/setup-pythonto fail on Debian-based self-hosted runners with:Requested additions:
Justification:
Debian is one of the most widely deployed Linux distributions for self-hosted CI runners and server infrastructure. Ubuntu itself is derived from Debian and shares the same glibc/libc6 ABI, meaning the same build pipeline used to produce Ubuntu binaries should work for Debian with minimal changes. Without manifest entries for Debian,
setup-pythonperforms a platform detection check via/etc/os-release, finds no matching entry, and errors out — even though an Ubuntu 24.04 binary would run correctly on Debian 13. Users are forced to either switch their runner OS to Ubuntu or removesetup-pythonentirely and rely on the system Python, both of which are unnecessary workarounds given the binary compatibility.Are you willing to submit a PR?
Yes, open to contributing if the maintainers can provide guidance on the build matrix configuration for Debian targets.