RustAudio
Discussion about using the SDK validator for CI
I was thinking about using the validator from the SDK to guarantee that, by testing the examples, between PRs there are no protocol breakages. What's the best way to approach this? I'm not a fan of adding pre-compiled executables and use those for the validation, so the alternative would be to separately compile them as needed through some workflow.
What's your opinion on this @m-hilgendorf ?
The "proper" approach to this is to run a GH action that checks out the VST3 SDK repo, builds the validator from source, and caches the build artifacts to run it (using actions/cache or similar).
Another thing we can do is just host the validator binaries somewhere, since the SDK is big and building takes a long time, and I think caches are refreshed from time to time.
