-
Notifications
You must be signed in to change notification settings - Fork 828
[NFC] Add upcoming release section post 1.9 release #8107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
alsepkow
merged 8 commits into
microsoft:main
from
alsepkow:user/alsepkow/UpcomingRelease
Feb 3, 2026
Merged
[NFC] Add upcoming release section post 1.9 release #8107
alsepkow
merged 8 commits into
microsoft:main
from
alsepkow:user/alsepkow/UpcomingRelease
Feb 3, 2026
+12
−7
Conversation
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
Set DXIL version to 1.9 for SM6.9. Was previously 1.10. microsoft#8091
damyanp
approved these changes
Jan 28, 2026
bob80905
approved these changes
Jan 28, 2026
tex3d
reviewed
Jan 28, 2026
Update spirv-tools to the v2026.1 release in preparation for the Vulkan SDK release. This picks up fixes for recent regressions related to debug info. Co-authored-by: Nathan Gauër <brioche@google.com>
Contributor
Author
|
Got it, that makes more sense then. I'll move that section up. I was under the impression that you could still use them if you opted in.
________________________________
From: Tex Riddell ***@***.***>
Sent: Friday, January 30, 2026 10:54 AM
To: microsoft/DirectXShaderCompiler ***@***.***>
Cc: Alex Sepkowski ***@***.***>; Author ***@***.***>
Subject: Re: [microsoft/DirectXShaderCompiler] [NFC] Add upcoming release section post 1.9 release (PR #8107)
@tex3d commented on this pull request.
________________________________
In docs/ReleaseNotes.md<#8107 (comment)>:
@@ -17,6 +17,11 @@ The included licenses apply to the following files:
## Changelog
+### Upcoming Release
+
+Place release notes for the upcoming release below this line and remove this
+line upon naming the release. Refer to previous for appropriate section names.
Are those experimental features not available in the release bits?
Correct. You can't target SM 6.10 in the that release.
—
Reply to this email directly, view it on GitHub<#8107 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABK4EWYUL5HJMW7X2JPF7VT4JOSHDAVCNFSM6AAAAACTDMWZM2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTOMRZHA3TSMJWGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
tex3d
approved these changes
Feb 3, 2026
Contributor
tex3d
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
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.
Add an 'Upcoming Release' section back into the release notes.