ci: pin latest MSVC matrix entry to windows-2022 (14.44)#243
Conversation
The windows-2025 runner label transiently resolved to a windows-2025-vs2026 image (Visual Studio 18 preview, MSVC 14.50) instead of the documented VS 2022 image, breaking the configure step because the hardcoded "Visual Studio 17 2022" generator can't match a VS 18 install. Pin the latest MSVC entry to windows-2022, which has VS 2022 stable, until VS 18 reaches RTM and CMake ships the corresponding generator. Also bump the matrix version label from 14.42 to 14.44 so the job name matches the toolset actually shipped on windows-2022 (14.44.35207).
|
An automated preview of the documentation is available at https://243.corosio.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-05-05 23:08:25 UTC |
|
GCOVR code coverage report https://243.corosio.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-05-05 23:16:12 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #243 +/- ##
========================================
Coverage 77.71% 77.71%
========================================
Files 96 96
Lines 7298 7298
Branches 1787 1787
========================================
Hits 5672 5672
Misses 1108 1108
Partials 518 518 Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
The windows-2025 runner label transiently resolved to a windows-2025-vs2026 image (Visual Studio 18 preview, MSVC 14.50) instead of the documented VS 2022 image, breaking the configure step because the hardcoded "Visual Studio 17 2022" generator can't match a VS 18 install.
Pin the latest MSVC entry to windows-2022, which has VS 2022 stable, until VS 18 reaches RTM and CMake ships the corresponding generator. Also bump the matrix version label from 14.42 to 14.44 so the job name matches the toolset actually shipped on windows-2022 (14.44.35207).