Skip to content

Carry matching headers in Vulkan update proposals - #19

Merged
antono3 merged 1 commit into
masterfrom
fix/complete-vulkan-proposals
Sep 29, 2026
Merged

antono3 merged 1 commit into
masterfrom
fix/complete-vulkan-proposals

Conversation

@antono3

@antono3 antono3 commented Sep 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Select the highest numeric upstream Vulkan-Docs tag and reject downgrades.
  • Generate with pinned V 0.5.2 and pair each generated registry snapshot with matching Vulkan-Headers C headers.
  • Compile the target module against those bundled headers and its pinned Volk sources, then include headers in the proposed antono2/vulkan PR.

This depends on antono2/vulkan#65, which permits generated PRs to carry the matching headers and removes the hard-coded version in its setup assertion.

Verification

  • Workflow YAML and embedded Bash syntax parsed.
  • git diff --check passed.
  • Upstream tag selection currently resolves to v1.4.364.

After both PRs merge, I will run the update workflow manually and review the generated target PR and CI.

@antono3
antono3 merged commit 1cb3f32 into master Sep 29, 2026
9 checks passed
@antono3
antono3 deleted the fix/complete-vulkan-proposals branch September 29, 2026 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants