Feedback or Inquiry
I would like to update our Windows CI configuration to use the newer Windows runner image.
Currently, there is a notice that windows-2025 requests are being redirected to windows-2025-vs2026. To avoid ambiguity and make the workflow configuration explicit, we should update the relevant workflow files to use:
runs-on: windows-2025-vs2026
This will ensure the CI environment matches the intended Windows Server 2025 image with Visual Studio 2026 support.
Additional Information
GitHub Actions has introduced the windows-2025-vs2026 runner image, and windows-2025 / windows-latest are being migrated to Visual Studio 2026 by default. Updating the workflow now should help avoid unexpected CI behaviour during or after the migration period.
Feedback or Inquiry
I would like to update our Windows CI configuration to use the newer Windows runner image.
Currently, there is a notice that
windows-2025requests are being redirected towindows-2025-vs2026. To avoid ambiguity and make the workflow configuration explicit, we should update the relevant workflow files to use:This will ensure the CI environment matches the intended Windows Server 2025 image with Visual Studio 2026 support.
Additional Information
GitHub Actions has introduced the
windows-2025-vs2026runner image, andwindows-2025/windows-latestare being migrated to Visual Studio 2026 by default. Updating the workflow now should help avoid unexpected CI behaviour during or after the migration period.