Describe the bug
When performing migrations for the first time, it fails on an exception caused by a change from Django 4.0 and since the requirements does not set any version rule for Django, it may install the 4.0 (if project does not already pin it).
To Reproduce
Steps to reproduce the behavior:
Clone repository
Execute "make install"
Fail with exception during migrations
Expected behavior
At least, a version rules should be "<4.0" or better we include support for Django 4.0 but it must not drop support for Django 3.x
Describe the bug When performing migrations for the first time, it fails on an exception caused by a change from Django 4.0 and since the requirements does not set any version rule for Django, it may install the 4.0 (if project does not already pin it).
To Reproduce Steps to reproduce the behavior:
Expected behavior At least, a version rules should be "<4.0" or better we include support for Django 4.0 but it must not drop support for Django 3.x
Versions: