Skip to content

ci: weekly SDK compliance sync via supabase/sdk reusable workflow#1606

Merged
spydon merged 3 commits into
mainfrom
chore/weekly-compliance-sync
Jul 21, 2026
Merged

ci: weekly SDK compliance sync via supabase/sdk reusable workflow#1606
spydon merged 3 commits into
mainfrom
chore/weekly-compliance-sync

Conversation

@spydon

@spydon spydon commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

What

Adds a weekly workflow that keeps sdk-compliance.yaml in sync with new capability IDs added to the canonical spec at https://github.com/supabase/sdk.

The sync logic lives centrally in supabase/sdk as a reusable workflow (see supabase/sdk#65), mirroring the existing validate-sdk-compliance-dart.yml pattern. This repo just adds a thin caller:

  • .github/workflows/sync-compliance.yml — runs Mondays 06:00 UTC (and on manual dispatch), calls supabase/sdk/.github/workflows/sync-sdk-compliance.yml@main, passing this repo's APP_ID/PRIVATE_KEY app-token secrets so the sync PR is opened under our own token.

The reusable workflow diffs the canonical feature IDs against the keys already in sdk-compliance.yaml, inserts any missing ones as not_implemented next to their area.group. siblings (correct section, no guessing), and opens/updates a PR here.

Why centralized

The diff/insert logic is language-agnostic, so it belongs in supabase/sdk where every SDK can share one implementation. Each SDK repo adds the same thin caller and runs on its own token, so no cross-repo permissions are needed.

Notes

@spydon
spydon requested a review from a team as a code owner July 16, 2026 12:51
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Added automated weekly compliance synchronization.
    • Added the ability to trigger compliance synchronization manually.
    • Improved workflow permissions and secure credential handling for synchronization tasks.

Walkthrough

Adds a GitHub Actions workflow named for compliance synchronization. It runs weekly on Mondays at 06:00 UTC or through manual dispatch, grants write permissions for repository contents and pull requests, and delegates execution to supabase/sdk’s reusable sync-sdk-compliance.yml workflow with APP_ID and PRIVATE_KEY 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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 37-70: Update the workflow before the “Append new capability IDs”
step to detect whether the sync branch already exists remotely, securely fetch
it, and check it out when present; otherwise create the branch from the default
branch. Run sync_compliance_matrix.py against that checked-out branch so
existing manual triage is preserved, and update the “Create pull request” step
to push without relying on a force-with-lease against an unavailable tracking
reference.
🪄 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: 3deb1d1d-389f-444d-98b9-2697443b9bdd

📥 Commits

Reviewing files that changed from the base of the PR and between 6e11db6 and ac69fd1.

📒 Files selected for processing (2)
  • .github/scripts/sync_compliance_matrix.py
  • .github/workflows/sync-compliance.yml

Comment thread .github/workflows/sync-compliance.yml Outdated
@spydon spydon changed the title ci: weekly sync of new capability IDs from canonical spec ci: weekly SDK compliance sync via supabase/sdk reusable workflow Jul 16, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-16: Update the reusable workflow reference in
sync-compliance.yml from the mutable main branch to a reviewed, full immutable
commit SHA, preserving the existing workflow path, secrets, and permissions.
🪄 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: 88d8dfb8-7b4c-49eb-9272-6c1186dca42b

📥 Commits

Reviewing files that changed from the base of the PR and between bd0d866 and 1ccd322.

📒 Files selected for processing (1)
  • .github/workflows/sync-compliance.yml

Comment thread .github/workflows/sync-compliance.yml
@spydon
spydon merged commit 2ec8aa6 into main Jul 21, 2026
22 checks passed
@spydon
spydon deleted the chore/weekly-compliance-sync branch July 21, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants