We could add this migration, but the issue with this is that those using Django < 4 will generate a new migration again.
Add one no-op migration that will work for both versions, adding the related_name in neighbours = models.ManyToManyField("self", related_name='_cities_country_neighbours_+' This way it won't check for new migration in both Django versions.
Let me know which is the preferred way and if I can help.
Checklist
master
branch of django-cities.Steps to reproduce
When using Django >= 4,
makemigrations
generates a new migration, and our CI fails when checking pending migrationsmakemigrations --check
Proposed solutions
Django 4 made a change on the migration autodetector and generates no-op migration for some models: https://docs.djangoproject.com/en/4.1/releases/4.0/#migrations-autodetector-changes
related_name
inneighbours = models.ManyToManyField("self", related_name='_cities_country_neighbours_+'
This way it won't check for new migration in both Django versions.Let me know which is the preferred way and if I can help.