Python <3.10 EOL versions accepted for branch builds

[MikeMcC399]

Version

Branches v20.x, V22.x, V24.x, V25.x & main

Platform

Generic Unix

Subsystem

build

Expected behavior

Node.js should not accept Python versions <3.10 in each of the supported branches' version of the configure shell script.

Each of the branches BUILDING.md > Unix prerequisites document section contains the requirement text:

• A supported version of Python
  * For test coverage, your Python installation must include pip.

Python released versions, listed as supported by the Python organization, range from Python 3.14 down to Python 3.10.

Python versions <3.10 have already reached end of life transition and are therefore unsupported:

Python version	End of life
3.6	2021-12-23
3.7	2023-06-27
3.8	2024-10-07
3.9	2025-10-31

Instead

Branch	Shell script	Allows Python
v20.x	configure	>=3.6 <=3.13
v22.x	configure	>=3.8 <=3.13
v24.x	configure	>=3.9 <=3.13
v25.x	configure	>=3.9 <=3.14
main	configure	>=3.9 <=3.14

Related

#60874 for missing Python 3.14 in LTS branches v20.x, v22.x & v24.x.

[aduh95]

I think this is a non-issue. The goal is to not unnecessary break downstream builders, if they are using unsupported Python versions that doesn't concern us. In #60431, we documented as a guarantee:

node/.github/workflows/tools.yml

Line 198 in f9f343f

# Node.js can be built with the same env along the whole release line life – or

Breaking compat on existing release lines would not be acceptable. If the goal of this issue is to discuss future release lines (and main), then we should rename the issue.

[MikeMcC399]

@aduh95

Thank you for highlighting the policy for retaining compatibility in released lines. I'll close this issue and re-submit it as two separate issues:

1. mismatch between BUILDING documentation and allowed Python versions in existing release lines - as a documentation issue
2. possible removal of Python 3.9 from main branch for future release lines Python 3.9 EOL accepted for build in main branch #60919