ci: weekly SDK compliance sync via supabase/sdk reusable workflow#2534
Merged
Conversation
|
Caution Review failedAn error occurred during the review process. Please try again later. 📝 WalkthroughWalkthroughAdds the “Sync SDK Compliance Matrix” GitHub Actions workflow. It runs weekly on Mondays at 06:00 UTC or through manual dispatch, grants contents and pull-request write permissions, and delegates execution to the reusable SDK compliance workflow on the master branch. Client credentials are forwarded through repository secrets. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/sync-compliance.yml:
- Around line 13-18: Update the reusable workflow reference in the sync
compliance workflow to replace the mutable `@main` tag with the reviewed,
immutable commit SHA for sync-sdk-compliance.yml. Keep the existing inputs and
forwarded secrets unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 06026a11-e280-4134-b341-5a0d27a0e1fc
📒 Files selected for processing (1)
.github/workflows/sync-compliance.yml
![depthfirst-app[bot]](https://avatars.githubusercontent.com/in/1021002?s=60&v=4){kind=small}
|
Coverage is 80.62% — ci/sync-compliance-caller into master. No base build found for |
…68fd6b583db0604ddce8af
Contributor
|
The following capabilities are marked
These may have been renamed, removed, or never registered. Please update the capability matrix. |
mandarini
approved these changes
Jul 21, 2026
mandarini
approved these changes
Jul 21, 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
3 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.
Adds a weekly workflow that keeps this repo's
sdk-compliance.yamlin sync with new capability IDs from the canonical spec at https://github.com/supabase/sdk.It's a thin caller for the reusable workflow added in supabase/sdk#65, mirroring the existing
validate-capabilities.ymlpattern. On a weekly cron it checks out the canonical spec, inserts any missing feature IDs asnot_implementednext to theirarea.group.siblings, and opens a PR here for triage.APP_CLIENT_ID/PRIVATE_KEY) to open the PR, so no cross-repo permissions are needed.not_implemented; real status and symbols are triaged by a maintainer.Depends on supabase/sdk#65 merging first (the
@mainreference resolves once it lands).