Greetings, Django does not currently support designating unapplied squashed migrations as dependencies.
This feels like bad behaviour, especially since `makemigrations` will reference a squashed migration by default if it has already been applied locally. I've made a ticket <https://code.djangoproject.com/ticket/25945> for this, along with submitting a patch <https://github.com/django/django/pull/5939> that addresses the issue by recursively rerouting dependencies on an unapplied squashed migration to that migration's applicable dependent and replaced migrations. Would really appreciate it if I could get some feedback on my approach to tackling the issue, and hopefully some thumbs up towards getting it merged! :) Cheers, Jarek -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0f922ff3-e18b-4e23-823e-d65f9b813adb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
