Skip to content

build,win: update WinGet configurations to Python 3.15 - #67431

Merged
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
MikeMcC399:winget-configuration-python3.15
Nov 19, 2026
Merged

nodejs-github-bot merged 1 commit into
nodejs:mainfrom
MikeMcC399:winget-configuration-python3.15

Conversation

@MikeMcC399

Copy link
Copy Markdown
Member

Refs: #65750

Situation

The BUILDING > Windows Prerequisites documentation section 2: Automated install with WinGet, using the .configurations files, installs Python 3.14.

Python 3.15 was released on 2026-10-09 and #65750 allows its usage to build Node.js.

With some delay, Python 3.15.x (3.15.2) is now available as a WinGet package:

winget search --id Python.Python.3.15
Name        Id                 Version Source
----------------------------------------------
Python 3.15 Python.Python.3.15 3.15.2  winget

The .configurations continue to install Visual Studio 2022 Build Tools. Microsoft supports Visual Studio 2022 for the remainder of the 10-year product lifecycle until January 2032. This covers the lifetime of all of the current Node.js release lines (last EOL is Node.js 27 on 2030-04-30).

Change

Update to Python 3.15 in:

Note also in the above documentation that an elevated (Administrator) PowerShell terminal window is necessary to execute the configurations, otherwise VSComponents fail to install.

Verification

Ensure that Python, Visual Studio Build Tools, Rust, nasm and git are not already installed. Uninstall using Settings > Apps > Install apps if necessary.

Follow the instructions in 2: Automated install with WinGet to install the Build Tools configuration in Windows 11 26H2 in an Administrator PowerShell 7 terminal:

winget configure .\.configurations\configuration.vsBuildTools.dsc.yaml

Backporting

Prerequisite is backport of #65750.

Do not backport to maintenance LTS v22.x since the configuration installs the Windows 11 SDK which conflicts with the documented Supported toolchains. For LTS v22.x manual installation of Windows prerequisites can be used instead.

Branch Supported toolchains Allows Python 3.15
v27.x Visual Studio 2022 or 2026 with the Windows 11 SDK on a 64-bit host yes
v26.x Visual Studio 2022 or 2026 with the Windows 11 SDK on a 64-bit host yes
v24.x Visual Studio 2022 or 2026 with the Windows 10 or 11 SDK on a 64-bit host pending backport #65750
v22.x Visual Studio 2022 with the Windows 10 SDK on a 64-bit host pending backport #65750

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/build
  • @nodejs/tsc

@MikeMcC399 MikeMcC399 self-assigned this Nov 12, 2026
@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to Node.js builds or CI infrastructure. doc Issues and PRs related to Node.js documentation. labels Nov 12, 2026
Signed-off-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com>
@MikeMcC399
MikeMcC399 force-pushed the winget-configuration-python3.15 branch from 8218842 to 247b377 Compare November 12, 2026 08:48
@MikeMcC399 MikeMcC399 added python PRs and issues that require attention from people who are familiar with Python. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. labels Nov 12, 2026
@MikeMcC399
MikeMcC399 marked this pull request as ready for review November 12, 2026 08:50
@MikeMcC399

Copy link
Copy Markdown
Member Author

@StefanStojanovic

I don't know if there are any users of these Windows configurations, as there have never been any comments on their usage. I don't use them personally and prefer instead to manually install on my test systems. In CI it's a different story, for instance Visual Studio is pre-installed in GitHub Actions, like git etc. For Python there's a separate action.

Nevertheless, since I previously updated the configurations, I wanted to keep them current, and so I've bumped Python to 3.15.

Microsoft has a confusing message of where they are going with Visual Studio 2026. Previously they said they were going to release Visual Studio 2027 around this time, but that hasn't happened. I've left the configuration using Visual Studio 2022, which covers the whole required lifetime of current Node.js release lines.

@StefanStojanovic StefanStojanovic left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @MikeMcC399, I am also not sure about these scripts' usage, but I know when we were adding them, they were tested and worked, and I'd expect the same to be the case now. Anyway, they are an actively supported way of setting up the developer environment and, as such, should be updated in PRs like this.

@MikeMcC399 MikeMcC399 added commit-queue PRs queued for automated landing through the Commit Queue. author ready PRs with CI started, the required approvals, and no outstanding review comments. labels Nov 17, 2026
@nodejs-github-bot nodejs-github-bot added the lacks-second-approval Commit Queue PRs awaiting a second collaborator approval or completion of the required wait. label Nov 17, 2026
@nodejs-github-bot
nodejs-github-bot merged commit 4f37a6a into nodejs:main Nov 19, 2026
50 checks passed
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Landed in 4f37a6a

@nodejs-github-bot nodejs-github-bot removed commit-queue PRs queued for automated landing through the Commit Queue. lacks-second-approval Commit Queue PRs awaiting a second collaborator approval or completion of the required wait. labels Nov 19, 2026
@MikeMcC399
MikeMcC399 deleted the winget-configuration-python3.15 branch November 19, 2026 09:02
aduh95 pushed a commit that referenced this pull request Nov 19, 2026
Signed-off-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com>
PR-URL: #67431
Refs: #65750
Reviewed-By: Stefan Stojanovic <stefan.stojanovic@janeasystems.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. build Issues and PRs related to Node.js builds or CI infrastructure. doc Issues and PRs related to Node.js documentation. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. python PRs and issues that require attention from people who are familiar with Python.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants