I am also super inter interested in the question
I am a big fan of migrations now that I understood I could also use them for updating db and content, and I very much like the reliability they give me so I can work on changes, then deploy them on my staging environnement and then production without a doubt that the changes in the database will be made as they should. And while I have deployments automatised, I did not yet manage to automatise that part.
Right now I use gitlab CI/CD jobs for deployments, but I still have to go launch the migrations manually.
In my thinking, I considered at least doing a php spark migrate status to warn migrations were needed but I dropped it because I was not managing to get Gitlab to do it (forgot for which reason exactly).
