Project documentation: mention Windows 11 SDK 10.0.26100 as the latest release#17378
Merged
Conversation
See test results for failed build of commit f9246c964c |
seanbudd
approved these changes
Nov 10, 2024
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.
Link to issue number:
Closes #17377
Summary of the issue:
The latest Windows 11 SDK is listed as build 22621.
Description of user facing changes
None
Description of development approach
Update Windows 11 SDK build to 10.0.26100 (24H2).
Testing strategy:
Building: make sure NVDA is built with Windows 11 SDK 10.0.26100 (it's been done on Appveyor for some time).
Known issues with pull request:
None
Code Review Checklist:
@coderabbitai summary