ci: test windows-2025-vs2026 runner ahead of June 2026 migration#76
Merged
Conversation
GitHub Actions is migrating windows-latest and windows-2025 to use Visual Studio 2026 by default, rolling out June 8-15, 2026. Opt into the new image early via the windows-2025-vs2026 label to surface any breakage before the automatic switchover.
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
1 participant
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
ci.ymlfromwindows-latesttowindows-2025-vs2026to opt into the new VS 2026 image early.windows-latest/windows-2025to VS 2026 by default during June 8–15, 2026 (changelog).Notes
bun build --compile, which produces a self-contained binary without invoking MSVC. Since nothing else in the toolchain depends on Visual Studio, the image swap is likely a no-op for these jobs.