We're currently using packages.lunarg.com/vulkan releases to get SPIRV-Tools in our CI environment. Those releases aren't very frequent, which is problematic when developing new features, see e.g. #3735 .
See if we can instead build the SPIRV-Tools main branch in CI. We'd probably want some kind of build cache to avoid burning many credits on repeatedly building the same thing, or running out of cycles for the longer-running in-tree jobs.
We're currently using packages.lunarg.com/vulkan releases to get SPIRV-Tools in our CI environment. Those releases aren't very frequent, which is problematic when developing new features, see e.g. #3735 .
See if we can instead build the SPIRV-Tools
mainbranch in CI. We'd probably want some kind of build cache to avoid burning many credits on repeatedly building the same thing, or running out of cycles for the longer-running in-tree jobs.