Repository navigation
feat: add default_privileges_expose_new_tables lint (0033) - #216
Open
mateuszingano wants to merge 1 commit into
Open
mateuszingano wants to merge 1 commit into
mateuszingano wants to merge 1 commit into
Conversation
mateuszingano
force-pushed
the
feat/default-privileges-lint
branch
from
November 17, 2026 18:47
ab11458 to
81f99be
Compare
This branch has not been deployed
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
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.
after oct 30 new tables need an explicit grant, and the quick fix a lot of people reach for when they hit the first 42501 is just putting the old default back:
that makes the error go away, but every table created after that is exposed again on creation, rls or not. no current lint catches it because nothing is exposed yet at the moment the default is added.
this one flags table defaults in
pg_default_aclthat grant to anon, authenticated or PUBLIC, in a schema frompgrst.db_schemas(or with noin schema). it skips defaults owned by supabase_/pg_ roles since the project owner can't change those, and service_role-only defaults.a couple of notes: