chore: update sdk-compliance.yaml for renamed capability matrix IDs - #1184
Merged
Conversation
supabase/sdk#74 renames/splits several feature IDs. Updates references here so CI's capability compliance validator doesn't fail on unknown IDs: - auth.sign_in.reset_password -> auth.sign_in.send_password_reset_email - realtime.channel.send -> realtime.channel.broadcast - storage.file_buckets.list_files_paginated merged into list_files - storage.analytics.iceberg_namespace split into create_namespace/list_namespaces/delete_namespace - storage.analytics.iceberg_table split into create_table/list_tables/load_table/update_table/rename_table/delete_table No SDK code changes — only the capability declarations. See supabase/sdk#74 and https://linear.app/supabase/issue/SDK-1439 for context.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe SDK compliance registry now uses canonical identifiers for password reset and realtime broadcast capabilities. It replaces Iceberg namespace and table entries with explicit unimplemented analytics operations for namespace and table management. Existing implementation status and symbol mapping remain unchanged for the password reset capability. ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
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 |
Contributor
|
The following capabilities are marked
These may have been renamed, removed, or never registered. Please update the capability matrix. |
Coverage Report for CI Build 31162668609Warning No base build found for commit Coverage: 83.893%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
mandarini
approved these changes
Aug 7, 2026
grdsdev
enabled auto-merge (squash)
August 7, 2026 09:57
grdsdev
added a commit
that referenced
this pull request
Aug 10, 2026
The 5 IDs the sync bot added (auth.sign_in.reset_password, realtime.channel.send, storage.file_buckets.list_files_paginated, storage.analytics.iceberg_namespace, storage.analytics.iceberg_table) are not new — they're the pre-rename names already retired in 450a8fc (#1184) per supabase/sdk#74. The bot resynced them because our caller workflow doesn't override the reusable workflow's sdk-ref input, so it inherits that pinned commit's baked-in default (faba359a, 2026-07-20), which predates the #74 rename. Pinning sdk-ref explicitly to a current supabase/sdk main SHA fixes the root cause.
grdsdev
added a commit
that referenced
this pull request
Aug 11, 2026
* chore: sync new capability IDs from canonical spec * chore: drop stale duplicate capability IDs, pin sync to current sdk main The 5 IDs the sync bot added (auth.sign_in.reset_password, realtime.channel.send, storage.file_buckets.list_files_paginated, storage.analytics.iceberg_namespace, storage.analytics.iceberg_table) are not new — they're the pre-rename names already retired in 450a8fc (#1184) per supabase/sdk#74. The bot resynced them because our caller workflow doesn't override the reusable workflow's sdk-ref input, so it inherits that pinned commit's baked-in default (faba359a, 2026-07-20), which predates the #74 rename. Pinning sdk-ref explicitly to a current supabase/sdk main SHA fixes the root cause. * ci: track supabase/sdk main for sync-compliance sdk-ref supabase/sdk is internal (same org, same review process), so treating it like an untrusted third party by pinning to a SHA isn't buying safety here. It does cost freshness: the reusable workflow's own baked-in sdk-ref default is a one-time pin upstream never refreshes, and supabase/sdk has no tags/releases for anything to key an auto-bump off of, so a fixed SHA here would just go stale again on its own schedule. Tracking main avoids that. * chore: drop explanatory comment from sdk-ref * ci: bump sync-sdk-compliance pin to the sdk-ref: main fix supabase/sdk#79 fixes the reusable workflow's own sdk-ref default (was stuck on the stale faba359a pin since 2026-07-20). Point at that fix commit directly and drop our local sdk-ref: main override, since it's now the workflow's default. Note: 72fda7c is currently on supabase/sdk's unmerged PR #79. Re-pin to the actual main commit once that merges. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Guilherme Souza <guilherme@supabase.io>
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.
Summary
supabase/sdk#74 renames/splits several feature IDs in the canonical capability matrix. This updates
sdk-compliance.yamlso the SDK compliance CI check doesn't fail on unknown IDs once that PR merges. No SDK code changes.auth.sign_in.reset_password→auth.sign_in.send_password_reset_emailrealtime.channel.send→realtime.channel.broadcaststorage.file_buckets.list_files_paginatedmerged intolist_filesstorage.analytics.iceberg_namespacesplit intocreate_namespace/list_namespaces/delete_namespace(same status replicated across all three — not yet divided per-operation)storage.analytics.iceberg_tablesplit intocreate_table/list_tables/load_table/update_table/rename_table/delete_table(same treatment)Context: SDK-1439
Test plan
npm run validate-compliancefromsupabase/sdk(branch with Which url should i use in redirect url to implement social auth? #74's changes):OK — compliance file is valid.