supabase-migration

To prevent unsafe direct DDL execution, create migrations using the supabase migration new command and apply schema changes through a CI/CD pipeline for controlled deployments. This enforces safe, compliant Supabase migrations by standardizing procedures.

The best way to secure database functions during a Supabase migration is to enforce search_path discipline and ensure views are securely defined. Proper object ownership must also be guarded to maintain predictable deployments and schema safety.

You need to use supabase migration new whenever you are creating database functions, modifying database schema, or performing operations like CREATE FUNCTION, ALTER TABLE, and CREATE INDEX to ensure changes are tracked and safely deployed.

Yes, Supabase migration tooling supports linting migrations before deployment. Linting checks schema and ownership guidelines, view security settings, and sequence synchronization to ensure predictable and safe CI/CD deployments.

You should enforce search_path discipline in Supabase database functions to prevent security vulnerabilities and ensure predictable execution. This discipline is a core rule for maintaining secure, compliant migrations during local development and CI/CD deployments.