ci: weekly SDK compliance sync via supabase/sdk reusable workflow#1128
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds a GitHub Actions workflow named “Sync SDK Compliance Matrix.” It runs weekly on Mondays at 06:00 UTC or through manual dispatch, grants contents and pull request write permissions, and invokes a pinned reusable SDK compliance workflow while forwarding the required application 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 |
There was a problem hiding this comment.
Pull request overview
Adds an automated GitHub Actions workflow to keep this repository’s sdk-compliance.yaml synchronized with newly introduced capability IDs from the canonical spec in supabase/sdk, by delegating to the reusable workflow introduced in supabase/sdk#65.
Changes:
- Adds a new scheduled + manually-dispatchable workflow to sync SDK compliance IDs weekly.
- Configures the job to call
supabase/sdk’s reusablesync-sdk-compliance.ymlworkflow. - Passes GitHub App credentials (from repo secrets) to allow the workflow to open PRs for triage.
Coverage Report for CI Build 29841381594Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage decreased (-0.1%) to 83.593%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions217 previously-covered lines in 8 files lost coverage.
Coverage Stats
💛 - Coveralls |
…68fd6b583db0604ddce8af
| permissions: | ||
| contents: write | ||
| pull-requests: write | ||
| uses: supabase/sdk/.github/workflows/sync-sdk-compliance.yml@faba359a57d270bbbf68fd6b583db0604ddce8af # main |
|
The following capabilities are marked
The following capabilities are marked
These may have been renamed, removed, or never registered. Please update the capability matrix. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
.github/workflows/sync-compliance.yml:13
- PR description says the reusable workflow reference will be
@mainonce supabase/sdk#65 lands, but this workflow is pinned to a specific commit SHA. Please clarify intent: either update the PR description to match the pin, or switch thisuses:ref to@main/a tagged release if you want automatic updates.
uses: supabase/sdk/.github/workflows/sync-sdk-compliance.yml@faba359a57d270bbbf68fd6b583db0604ddce8af
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_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).