@selvajs/supabase-provider 0.12.0 → 0.13.1

package/supabase/migrations/{0002_definition_version_schema.sql → 20260529202220_selva_definition_version_schema.sql}

@@ -10,7 +10,7 @@
 -- by 0001_initial.sql — this closes that drift.
 -- ============================================================================
 
-alter table public.definition_versions
+alter table selva.definition_versions
 	add column if not exists change_note text,
 	add column if not exists schema jsonb,
 	add column if not exists schema_extracted_at timestamptz;

package/supabase/migrations/20260531120000_set_updated_at_search_path.sql

@@ -0,0 +1,11 @@
+-- ============================================================================
+-- Harden selva.set_updated_at() with an immutable search_path
+--
+-- The trigger function shipped in 20260425155514_selva_initial.sql had a
+-- role-mutable search_path (Supabase linter 0011_function_search_path_mutable).
+-- The body only touches `new` and `now()` — no schema-qualified objects — so
+-- pinning search_path to empty closes the privilege-escalation vector without
+-- changing behaviour. Triggers that reference this function are unaffected.
+-- ============================================================================
+
+alter function selva.set_updated_at() set search_path = '';