Postgres uuid field in an earlier migration

This sounds like your production target has no real-world data yet? If thats the case, you could either try sqashing the migrations on that model into just one initial (more friendly to all dev instances, but caution - needs to be applied on all dev instances before you can remove the old migration cascade), or go with a faked initial (more disruptive, would not be my first choice).

If there is no real-world data yet at all, well - delete all migrations, remove db files on dev instances, and startover from scratch (makemigrations → migrate, creates initial migrations with uuid field in the first place).