Issue with pushing to production from a lovable project due to migration file name inconsistencies.
Hello, We're looking to migrate a project from lovable to a production environment but have some issues with some old Supabase migrations that lovable.dev has created in the incorrect naming convention.
There are a number of migrations which have a - instead of _ so get skipping during the Github action migration. Then subsequent correctly named migrations fail as tables dont exist.
Example incorrect: 20250610151444-cc6b0ded-dca4-406f-8861-ce919e4a92a9.sql
Correct should be: 20250610151444_cc6b0ded-dca4-406f-8861-ce919e4a92a9.sql
format: YYYYMMDDHHmmss_name.sql
We have tried to squash the migrations locally but as they are also incorrect it fails.
Please can someone advise the best approach to proceed?
Thanks!
Sam
There are a number of migrations which have a - instead of _ so get skipping during the Github action migration. Then subsequent correctly named migrations fail as tables dont exist.
Example incorrect: 20250610151444-cc6b0ded-dca4-406f-8861-ce919e4a92a9.sql
Correct should be: 20250610151444_cc6b0ded-dca4-406f-8861-ce919e4a92a9.sql
format: YYYYMMDDHHmmss_name.sql
We have tried to squash the migrations locally but as they are also incorrect it fails.
Please can someone advise the best approach to proceed?
Thanks!
Sam
