Uh oh!
There was an error while loading. Please reload this page.
GH-150605: use windows-2025 in GitHub Actions - #150606
Conversation
chris-eibl
commented
Jun 21, 2026
We're now almost a week past 15th, so pulling in main to try out ... |
webknjaz
commented
Jun 21, 2026
Could you explain the motivation? Are they sunsetting this runner label? If not, I don't see why what we have now needs to change. |
chris-eibl
commented
Jun 21, 2026
See the links given in the issue. I don't know whether the label If it stays, then this PR can be closed ofc ... |
chris-eibl
commented
Jun 21, 2026
|
There was a problem hiding this comment.
The announcement made it clear the old windows-2025-vs2026 label is for testing only:
Note: This label is meant for testing only. After the migration, this label will point to the
windows-2025image.
It may or may not go away, but let's use windows-2025 instead of the testing-only windows-2025-vs2026.
Uh oh!
There was an error while loading. Please reload this page.
Thanks @chris-eibl for the PR 🌮🎉.. I'm working now to backport this PR to: 3.15. |
GH-151939 is a backport of this pull request to the 3.15 branch. |
webknjaz
commented
Jun 23, 2026
Alright, then. Though, I'd prefer the specific label if it's kept since it is clearer about the runtime and is probably more likely to be immutable. |
use windows-2025 in GitHub Actions
Marking as draft until we really want to switch in mid-June.