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
6df9442cd0654462e5ee5fbd604198ab5013fa89
Sauci/docs/operations/database-migrations.md
T
jjbrunton 01bb8225ae chore(harness): make repository agent-ready 
Add concise routed context, task-aware agent roles, focused skills, and structured learning promotion.\n\nUnify local development and workspace tooling, add layered test and E2E verification, harden MCP authentication, and gate deployment behind verification and explicit production promotion.
2026-08-27 20:58:48 +01:00

844 B
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. Local verification must not link a remote project.

Reference in new issue View Git Blame Copy Permalink