Use windows-2022 runner for now#94
Merged
Merged
Conversation
windows-latest will switch to Visual Studio 2026 soon.
Member
|
Good catch. I've opened #96 to track the need to update the template to VSCode 2026, but this is a good workaround for the short term. |
freakboy3742
approved these changes
May 25, 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.
GitHub will migrate the
windows-latestrunner to Visual Studio 2026 soon: https://github.blog/changelog/2026-05-14-github-actions-upcoming-image-migrations/Continuing to use
windows-latestwill require the template to upgrade to the v145 version of VS build tools, but the ARM runner is unlikely to be upgraded at the same time despite being owned by GitHub now (they explicitly state no breaking changes will be introduced at the moment).Refs #96.
PR Checklist: