Hello 👋 I have a prisma migration problem / solution I want to get a sense check on. Currently, we have CI set to run migrations on a newly spun up docker container which helps with ensuring migrations take place in the right order. But we’re running into an issue where devs are generating migrations that break production (i.e. renaming column drops column and adds a new one rather than copy / rename). Is the best solution to write a CI job that does a dry run against staging/production where there is data to catch bad migrations? Thanks in advance!

Hey Arthur! It is generally a good idea to run migrations in CI against some kind of development or staging database before going to production. If you are hitting some situations where the experience could be improved, please open a feature request!

thank you!