Update CI to Windows Server 2025 with Visual Studio 2026 - #321
Open
shankarseal wants to merge 1 commit into
Open
Update CI to Windows Server 2025 with Visual Studio 2026#321shankarseal wants to merge 1 commit into
shankarseal wants to merge 1 commit into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 70c92899-1e48-48fe-9afa-5dc83fedfeb8
shankarseal
force-pushed
the
shankarseal-update-build-vs2026
branch
from
August 4, 2026 01:19
034c8d1 to
83036d2
Compare
LakshK98
approved these changes
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current CI uses
windows-2022runners with Visual Studio 2022 tooling. With Visual Studio 2026 now available as a public beta via thewindows-2025-vs2026runner image (actions/runner-images#13638), this PR migrates both build jobs to take advantage of the updated toolchain.Changes in
build.yml:runs-on:windows-2022->windows-2025-vs2026(bothbuild-vsandbuild-cmakejobs)"Visual Studio 17 2022"->"Visual Studio 18 2026"(all invocations)CMAKE_GENERATORenv var updated to match inbuild-cmakePLATFORM_TOOLSET:v143->v145(VS 2026 MSVC toolset)Note:
windows-2025-vs2026is currently a public beta image. Per the runner-images announcement,windows-latestandwindows-2025will default to this image starting mid-June 2026, at which point this label will resolve identically towindows-2025.