Move Windows CI to the windows-2025-vs2026 runner - #329
Merged
Conversation
GitHub is redirecting `windows-2025` runner requests to `windows-2025-vs2026` by 2026-06-15. Move on our own schedule rather than being silently redirected. Also bump the actionlint CI image to 20260529, whose actionlint knows the `windows-2025-vs2026` label so workflow linting still passes.
ponylang-main
added
the
discuss during sync
ponylang-main
removed
the
discuss during sync
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 is redirecting
windows-2025runner requests towindows-2025-vs2026by 2026-06-15. This moves us on our own schedule rather than being silently redirected.Also bumps the actionlint CI image to
20260529, whose bundled actionlint recognizes thewindows-2025-vs2026label so workflow linting continues to pass.