ci: use per-language SDK compliance workflow#1493
Merged
Merged
Conversation
1 task
grdsdev
approved these changes
Jun 30, 2026
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
2 participants
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
Updates the SDK compliance check to use the new per-language reusable workflow from
supabase/sdk. The singlevalidate-sdk-compliance.yml(which took alanguage:input and gated every step on it) has been split into one workflow per language (supabase/sdk#49).This drops the
language:input and points at the language-specific file.Important
Merge only after supabase/sdk#49 lands on
main, since the new workflow file must exist at@mainfor this reference to resolve.