.sql to seed the field or execute a script manually after the migration before proceeding. However, none of the solutions for seeding cover my case. I need to be able to execute a sequence of migrations without going 1 by 1 and manually running data migrations scripts inbetween. Basically, I want to create the field, seed the data and make it required in one migrate deploy step. How can I achieve that? Can I somehow associate a data migration script to every migration that gets executed automatically before the next migration or something? I can't use @default() as the data is calculated dynamically.