Skip to content
This repository was archived by the owner on May 30, 2026. It is now read-only.

Move Windows CI to the windows-2025-vs2026 runner#149

Merged
SeanTAllen merged 1 commit into
mainfrom
windows-2025-vs2026
May 30, 2026
Merged

Move Windows CI to the windows-2025-vs2026 runner#149
SeanTAllen merged 1 commit into
mainfrom
windows-2025-vs2026

Conversation

@SeanTAllen
Copy link
Copy Markdown
Member

GitHub is redirecting windows-2025 runner requests to windows-2025-vs2026 by 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 the windows-2025-vs2026 label so workflow linting continues to pass.

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 ponylang-main added the discuss during sync Should be discussed during an upcoming sync label May 29, 2026
@SeanTAllen SeanTAllen merged commit d170fac into main May 30, 2026
14 of 15 checks passed
@SeanTAllen SeanTAllen deleted the windows-2025-vs2026 branch May 30, 2026 00:13
@ponylang-main ponylang-main removed the discuss during sync Should be discussed during an upcoming sync label May 30, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants