GitHub is starting a migration of windows-latest to windows-2022:
https://github.blog/changelog/2022-01-11-github-actions-jobs-running-on-windows-latest-are-now-running-on-windows-server-2022/
actions/runner-images#4856
Migration starts now, and should finish by March 6. It is not clear if that timetable includes the -xl runners. Based on the fact that the ubuntu-latest-xl runners have not yet migrated to 20.04, which was "completed" in 2021-03-18 (and it is now 2022-01-15), the timing for the -xl images might be much slower.
UPDATE from GitHub: Our first goal is to GA Windows 2022 this quarter and then we will start the process of getting the XL pools ready.
It may be possible to lock to an older version with windows-2019-xl (as it appears those version-specific qualifiers work with ubuntu), but I have not tested that.
I have started testing some builds in 2022 and they are not going well, I'll try to document some issues here.
GitHub is starting a migration of
windows-latesttowindows-2022:https://github.blog/changelog/2022-01-11-github-actions-jobs-running-on-windows-latest-are-now-running-on-windows-server-2022/
actions/runner-images#4856
Migration starts now, and should finish by March 6. It is not clear if that timetable includes the
-xlrunners. Based on the fact that theubuntu-latest-xlrunners have not yet migrated to 20.04, which was "completed" in 2021-03-18 (and it is now 2022-01-15), the timing for the-xlimages might be much slower.UPDATE from GitHub: Our first goal is to GA Windows 2022 this quarter and then we will start the process of getting the XL pools ready.
It may be possible to lock to an older version with
windows-2019-xl(as it appears those version-specific qualifiers work with ubuntu), but I have not tested that.I have started testing some builds in 2022 and they are not going well, I'll try to document some issues here.