jjbrunton/Sauci
1
0 Fork 0
mirror of https://github.com/jjbrunton/Sauci.git synced 2026-10-31 18:19:43 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
d869592a8ba72943d5720307f1d2625fa56208f0
Sauci/docs/operations/database-migrations.md
T
jjbrunton 04dee69888 fix(ci): scope Terraform deployments 
Skip Terraform for function-only Supabase releases to avoid unrelated provider drift failures. Continue applying infrastructure for terraform path changes or explicit manual deployment requests.
2026-08-27 22:08:08 +01:00

1.1 KiB
Raw Blame History

Database migration safety

All schema changes are versioned local files under apps/supabase/migrations/.

Required workflow

  1. npm run db:migration:new -- <descriptive_name>
  2. Edit the generated local migration.
  3. Prefer idempotent SQL where semantics permit it.
  4. npm run db:reset against local Supabase.
  5. Run npm run test:supabase and affected application checks.
  6. Commit the migration with dependent code and types.

Forbidden paths

  • Never call a remote apply_migration MCP tool.
  • Never execute DDL through MCP SQL execution.
  • MCP SQL execution is read-only SELECT use only.
  • Never insert migration history manually except an explicitly approved repair.
  • Never hardcode a production URL in a migration or cron definition.

CI deploys committed migrations and Edge Functions to non-production after relevant pushes. Production promotion is a manual workflow dispatch. Terraform is applied only when files under terraform/ change, or when deploy_infrastructure is explicitly selected during a manual deployment. Local verification must not link a remote project.

Reference in new issue View Git Blame Copy Permalink