ci: switch to windows-2025-vs2026 ahead of VS 2026 migration#54
Merged
Conversation
…ration GitHub is migrating windows-latest to default to Visual Studio 2026 between June 8–15, 2026. Switch to windows-2025-vs2026 now so CI validates the action works on VS 2026 before the forced rollout. The action itself uses vswhere -latest and is not VS-version-specific, so no logic changes are needed — only the runner label. https://claude.ai/code/session_011WjuYJ2CQtQK1aE9gzeox8
…5-vs2026) Expand the x86/x64 matrix to cover both images so CI catches regressions on VS 2022 while also validating VS 2026 ahead of the windows-latest migration scheduled for June 8–15, 2026. https://claude.ai/code/session_011WjuYJ2CQtQK1aE9gzeox8
Add a runner compatibility table explaining how windows-latest migrates to VS 2026 (June 8–15, 2026) and that the action works with both versions without any configuration changes. Remove the hardcoded vs-version: '2022' from the example so it doesn't conflict with runners that only have VS 2026 installed. https://claude.ai/code/session_011WjuYJ2CQtQK1aE9gzeox8
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.
Summary
windows-latestandwindows-2025to use Visual Studio 2026 by default between June 8–15, 2026windows-latest→windows-2025-vs2026to proactively validate the action against VS 2026 before the forced rolloutsrc/main.ts) usesvswhere -latestand is not tied to any specific VS version, so no logic changes are required — only the runner label needs updatingTest plan
windows-2025-vs2026for both x86 and x64 matrix entrieswindows-11-armfor arm64 (unchanged)ml.exe(x86),ml64.exe(x64), andarmasm64.exe(arm64) are each found in PATH after the action runshttps://claude.ai/code/session_011WjuYJ2CQtQK1aE9gzeox8
Generated by Claude Code