Update Supabase guide for Data API grants, RLS, and publishable keys#453
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
benitav
reviewed
May 14, 2026
benitav
reviewed
May 14, 2026
…sync-ja/powersync-docs into supabase-guide-data-api-grants-rls
michaelbarnes
approved these changes
May 15, 2026
bean1352
added a commit
to powersync-ja/agent-skills
that referenced
this pull request
May 20, 2026
…able keys - Add Data API Grants section to supabase-auth.md explaining the Supabase default change (May 30 2026) and the explicit grant SQL required for supabase-js writes on new projects - Update uploadData() Important note to clarify that grants are checked before RLS; a missing grant causes 42501 before RLS is evaluated - Add publishable keys note after the fetchCredentials() JS/TS example - Update onboarding-supabase.md step 2 to mention publishable keys as the replacement for the legacy anon key on new Supabase projects Source: powersync-ja/powersync-docs#453
michaelbarnes
pushed a commit
to powersync-ja/agent-skills
that referenced
this pull request
May 27, 2026
…able keys (#32) - Add Data API Grants section to supabase-auth.md explaining the Supabase default change (May 30 2026) and the explicit grant SQL required for supabase-js writes on new projects - Update uploadData() Important note to clarify that grants are checked before RLS; a missing grant causes 42501 before RLS is evaluated - Add publishable keys note after the fetchCredentials() JS/TS example - Update onboarding-supabase.md step 2 to mention publishable keys as the replacement for the legacy anon key on new Supabase projects Source: powersync-ja/powersync-docs#453
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.
Supabase is changing the default for Data API exposure of public tables and has replaced the legacy anon key with publishable keys on new projects. Updating the guide so it works under both old and new defaults.
AI disclaimer: Used Claude to verify the documentation changes. I set up a brand new Supabase project and PowerSync instance to test the guide end to end too.