Revert to Windows-2022#1556
Merged
Merged
Conversation
awawa-dev
added a commit
that referenced
this pull request
Jun 30, 2026
awawa-dev
added a commit
that referenced
this pull request
Jul 1, 2026
* Fix 1 * Fix 2 * Fix 3 * Fix 4 * Fix 5 * Final time refactor * Fix warning * Revert to Windows-2022 (#1556)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Microsoft recently updated the Visual Studio environment on the latest GitHub Windows runners to VS2025 mid-cycle. This introduces significant risks of breaking changes and MSVC linking incompatibilities, particularly with our Qt dependencies fetched via
aqtinstall, which are currently built and validated against the VS2022 toolchain.While we appreciate Microsoft's enthusiasm for rapidly promoting VS2025, pushing a major toolchain upgrade onto existing runners without a proper transition period unnecessarily disrupts stable pipelines.
To ensure our CI remains reliable, predictable, and our Qt binaries continue to link correctly, we are locking the environment to the thoroughly tested VS2022 toolchain until a proper VS2025 migration can be validated.
Reference:
actions/runner-images#14017