Fix Windows CI: stop pinning CMake to the VS 2022 generator#1208
Merged
lightvector merged 1 commit intoJun 12, 2026
Merged
Conversation
The windows-latest runner image now ships Visual Studio 2026 only (actions/runner-images#14017), so configuring with -G "Visual Studio 17 2022" fails with "could not find any instance of Visual Studio". Drop the explicit generator and let CMake auto-detect the installed Visual Studio, keeping -A x64. https://claude.ai/code/session_018eaSTE1PhvV7SsiNyJrq76
ChinChangYang
added a commit
to ChinChangYang/KataGo
that referenced
this pull request
Jun 12, 2026
…tor#1208) The windows-latest runner image now ships Visual Studio 2026 only (actions/runner-images#14017), so configuring with -G "Visual Studio 17 2022" fails with "could not find any instance of Visual Studio". Drop the explicit generator and let CMake auto-detect the installed Visual Studio, keeping -A x64. https://claude.ai/code/session_018eaSTE1PhvV7SsiNyJrq76 Co-authored-by: Claude <noreply@anthropic.com>
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
3 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.
Summary
The
build-windowsCI job started failing at the CMake configure step:GitHub migrated the
windows-latestrunner image to Windows Server 2025 with Visual Studio 2026 only (rolled out June 8–15, 2026, see actions/runner-images#14017), so the hard-coded-G "Visual Studio 17 2022"generator no longer resolves.Fix
Drop the explicit generator from the Configure CMake step, keeping
-A x64. CMake auto-detects the newest installed Visual Studio (VS 2026 on the current image), and the job will survive future VS bumps on the runner image without further edits. All other steps (--config Releasebuild,Release/paths, DLL copy, tests) are generator-version-agnostic.Verification
workflow_dispatchrun on this branch: run 27383148471 — all 4 jobs passed, includingbuild-windows(configure under VS 2026, build, andkatago.exe runtestsall green).https://claude.ai/code/session_018eaSTE1PhvV7SsiNyJrq76
Generated by Claude Code