Schema Drift Between Stripe Sync Engine Installed Via Studio And Docker Due To Missing Version Pinning

Supabase does not expose or enforce a consistent version of stripe/sync-engine between the hosted Studio installation and the self-hosted Docker image. Migrations are applied from different upstream versions, leading to schema divergence. This is a design defect in integration version management within Supabase.

1. Install stripe/sync-engine via Supabase Studio on a hosted project. 2. Set up a local Supabase dev environment. 3. Run the stripe/sync-engine Docker image locally. 4. Observe schema mismatch errors and sync engine failure.

Hardcoding a version can cause drift if the hosted Studio upgrades to a newer sync-engine version and the config is not updated. Use a shared version variable and automated checks to prevent divergence. Rolling back requires reverting the version pin and recreating the schema from a baseline dump or running down migrations. Verify the Docker image tag exists for the pinned version; some older or non-standard versions may not be published. Concurrent updates by multiple developers may still diverge if the config is not version-controlled.