Skip to content

[windows] Add Windows Server 2025 with Visual Studio 2026#13635

Merged
erik-bershel merged 9 commits intoactions:mainfrom
shamil-mubarakshin:windows2025-add-vs2026
Feb 6, 2026
Merged

[windows] Add Windows Server 2025 with Visual Studio 2026#13635
erik-bershel merged 9 commits intoactions:mainfrom
shamil-mubarakshin:windows2025-add-vs2026

Conversation

@shamil-mubarakshin
Copy link
Copy Markdown
Contributor

Description

This PR adds windows-2025-vs2026 image generation template and contains corresponding code changes:

  • added toolset-2025-vs2026.json and build.windows-2025-vs2026.pkr.hcl
  • Visual Studio install script is refactored to correctly handle installChannelUri
  • Configure-ImageDataFile.ps1 and Install-AndroidSDK.ps1 are modified to support VS 2026 changes
  • updates to docs and Readme

Related issue:

Check list

  • Related issue / work item is attached
  • Tests are written (if applicable)
  • Documentation is updated (if applicable)
  • Changes are tested and related VM images are successfully generated

Copilot AI review requested due to automatic review settings February 5, 2026 16:48
erik-bershel
erik-bershel previously approved these changes Feb 5, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds support for a new Windows Server 2025 with Visual Studio 2026 runner image. The changes include a new toolset configuration, build template, and necessary modifications to installation scripts to support Visual Studio 2026's different bootstrapper URL pattern and channel configuration.

Changes:

  • Added toolset-2025-vs2026.json configuration with VS 2026 (version 18.x) and updated software versions
  • Refactored Visual Studio installation helper to support VS 2026's different bootstrapper URL pattern via the INSTALL_VS_2026 environment variable
  • Modified parameter naming from installChannel to installChannelUri for clarity and consistency
  • Added Android SDK cleanup logic to handle potential conflicts with VS workload installations
  • Updated documentation, README, workflows, and issue templates to include the new image variant

Reviewed changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
images/windows/toolsets/toolset-2025-vs2026.json New toolset configuration for VS 2026 with updated software versions
images/windows/toolsets/toolset-2025.json Updated parameter name from installChannel to installChannelUri
images/windows/toolsets/toolset-2022.json Updated parameter name from installChannel to installChannelUri
images/windows/templates/locals.windows.pkr.hcl Added win25-vs2026 configuration mapping
images/windows/templates/build.windows-2025-vs2026.pkr.hcl New Packer build template for VS 2026 image
images/windows/scripts/helpers/VisualStudioHelpers.ps1 Refactored to support VS 2026 bootstrapper URL and installChannelUri handling
images/windows/scripts/build/Install-VisualStudio.ps1 Updated to use new installChannelUri parameter
images/windows/scripts/build/Install-AndroidSDK.ps1 Added cleanup logic for previous cmdline-tools installations
images/windows/scripts/build/Configure-ImageDataFile.ps1 Added conditional logic for VS 2026 image labels and URLs
images/windows/Windows2025-VS2026-Readme.md New README documentation for the VS 2026 image
helpers/GenerateResourcesAndImage.ps1 Added Windows2025_vs2026 to ImageType enum and fixed packer pattern matching
README.md Added entry for windows-2025-vs2026 image in available images table
.github/workflows/windows2025-vs2026.yml New workflow for triggering VS 2026 image builds
.github/ISSUE_TEMPLATE/tool-request.yml Added VS 2026 option to affected images
.github/ISSUE_TEMPLATE/bug-report.yml Added VS 2026 option to affected images
.github/ISSUE_TEMPLATE/announcement.yml Added VS 2026 option to affected images

"version" : "2026",
"subversion" : "18",
"edition" : "Enterprise",
"channel": "stable",
Copy link

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

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

The Visual Studio channel is set to "stable" for VS 2026, but all other Visual Studio versions in this codebase use "release". This inconsistency should be verified - is "stable" the correct channel name for VS 2026, or should it be "release" to match the existing pattern?

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

VS 2026 has only Stable channel as of now. Will be changed to postGRO once available

@hugovk
Copy link
Copy Markdown
Contributor

hugovk commented Feb 5, 2026

This has been announced today: https://github.blog/changelog/2026-02-05-github-actions-early-february-2026-updates/

But it's not yet available, this job is waiting for a runner: https://github.com/python/cpython/actions/runs/21721176273/job/62651063296?pr=144516 / python/cpython#144516.

Was it announced prematurely and do we need this PR merging first?

And I expect likewise for macos-26-large and #13634?

Thanks!

@erik-bershel erik-bershel merged commit 71f0157 into actions:main Feb 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants