Prepare Vulkan v3.1.3 release - #59
Merged
Merged
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
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.
Summary
Prepare the Vulkan v3.1.3 patch release after the C
int/ V3 FD ABI correction in #58. Update the module version and pin CI's generator checkout to the merged Cint→i32fix from antono2/v_vulkan_bindings#16.The Vulkan registry and bundled headers remain at v1.4.363.
Verification
i32FD callers completed Vulkan–OpenCL memory sharing and semaphore handoff under V 0.5.2 and a locally patched V3 compiler.git diff --checkpasses.After this PR's checks pass, tag
v3.1.3to trigger the guarded release workflow. The OpenCL example dependency can then pin that tag.