Repository navigation
CI: Update to VS 2026 - #13543
Merged
Merged
CI: Update to VS 2026#13543
Conversation
This will also allow us to move to clang-format 22 which ships with VS 2026. * Update the CI image to windows-2025-vs2026 * Update VS generator to 2026 * Update Windows SDK to 26100
RytoEX
added
platform/windows
Warchamp7
reviewed
Jun 12, 2026
Warchamp7
approved these changes
Jun 12, 2026
Warchamp7
left a comment
Warchamp7
left a comment
Member
There was a problem hiding this comment.
Compiles and works on my end.
PatTheMav
approved these changes
Jun 12, 2026
BlueCheeseburger
pushed a commit
to BlueCheeseburger/obs-studio
that referenced
this pull request
Aug 22, 2026
CI: Update to VS 2026
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
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.
Description
Important
Because this updates
.github/workflows/sign-windows.yaml, the commit hash for consuming that must be updated, which means this requires a merge commit.Update CI to use VS 2026:
Motivation and Context
After the recent clang-format update in #13402, we discovered that the way we applied braces to only C++ is not supported by clang-format 19 (the version we currently use). It was added in clang-format 20. VS 2026 ships with clang-format 22.
windows-2025-vs2026image is now GA.windows-2025andwindows-latestto thewindows-2025-vs2026image in June.How Has This Been Tested?
Built on my fork's CI.
https://github.com/RytoEX/obs-studio/actions/runs/27319184501
I haven't done runtime tests.
Types of changes
Checklist: