Skip to main content

3.0.0 schema migrations (per database)

The Prisma schema migrations this release (2.0.0 → 3.0.0) introduces, one folder per database. Reference / review copy only — these are not applied from here.

How they run​

Migrations run automatically on deploy: each app's container entrypoint runs prisma migrate deploy on rollout. Locally we run prisma migrate deploy per app by hand (see DEPLOY-RUNBOOK.md §). Source of truth is apps/<app>/prisma/migrations/; re-copy here if regenerated.

DatabaseMigrations
ark-platform20260221153539_migration_notifications_to_party, 20260325000000_drop_auth_table, 20260520051241_connector_routing
ark-connector-bre20260224085825_create_rule_table
ark-connector-simplekyc20260223013224_init
ark-flows (ark-flows-api)20260519000000_init_workflow_state

Optional​

The ark-flows and ark-connector-bre databases (and their migrations) are optional — they are only required for clients using Ark Flows and/or the Business Rules Engine. A base deployment can skip creating those databases and running their migrations. Clients adopting these components later will need to update their setup and configuration to support them.

Warnings​

  • ark-platform/20260520051241_connector_routing is destructive — it DROPs BreConfig and Rule. Back up ark-platform first; rollback does not restore them.
  • ark-platform/20260221153539_migration_notifications_to_party adds Notification.partyId NOT NULL with no default — fails if Notification has rows (confirm SELECT COUNT(*) FROM dbo.Notification = 0).
  • New databases must already exist before migrate deploy (it creates schemas, not databases): ark-connector-simplekyc, ark-connector-bre, ark-flows.

Excluded​

ark-connector-message-media (and ark-connector-twilio) — the notification connectors are not part of this release, so their migrations/databases are intentionally omitted.