Closed istride closed 1 year ago
The issue is caused by incremented package version of django-translation-manager 1.3.0 which is incompatible with our current django version 3.1.*
It would be fix in the next release because we are using Django 3.2.* now, additionally we will lock the dependencies using pip-tools to avoid this issue in future.
Logs in production show that there are missing migrations in the latest release.
This must be addressed before the next release.
How can we avoid this happening again?