Skip to content

Record DB-03 legacy policy drop as a migration #219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Programcode merged 1 commit into from
Oct 23, 2026
Merged

Record DB-03 legacy policy drop as a migration #219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions ...d/20261023060000_drop_legacy_policies.sql → ...s/20261023080000_drop_legacy_policies.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,7 @@
-- DB-03 (proposed, destructive): drop policies that no migration created.
-- DB-03: drop policies that no migration created. Approved by Adam on
-- 23 Oct 2026; moved from supabase/proposed/. It was run by hand on staging
-- and production first, after shared links, role reads and usage counts were
-- tested on staging, so on both hosted projects this finds nothing to drop.
--
-- The QA run on 22 Oct 2026 found policies on production that are not in
-- staging or in supabase/migrations, including duplicate permissive ones on
Expand All @@ -24,7 +27,8 @@
-- caller's own rows: without user_roles_select_own, signed-in users could no
-- longer read their own role (SettingsPage and the curated_sources admin
-- policies depend on it), and a drifted copy would keep the leak this fixes.
-- Do a dry run first (BEGIN; ...; ROLLBACK;).
-- Running it again changes nothing: every drop is IF EXISTS and the kept
-- policies are never dropped.

DO $$
DECLARE
Expand Down
Loading