Based upon this pip dependency graph, upgrading from Django 3.2 to 4.1 should not be too troublesome from a deep perspective
(env) django-DefectDojo $: pipdeptree | grep Django -B 1
django-auditlog==2.2.1
- Django [required: >=3.2, installed: 3.2.16]
--
django-extensions==3.2.1
- Django [required: >=3.2, installed: 3.2.16]
--
django-filter==21.1
- Django [required: >=2.2, installed: 3.2.16]
--
django-polymorphic==3.1.0
- Django [required: >=2.1, installed: 3.2.16]
--
django-slack==5.18.0
- Django [required: >=3.2, installed: 3.2.16]
--
django-tagulous==1.3.3
- Django [required: >=2.2, installed: 3.2.16]
--
- defusedxml [required: >=0.4.1, installed: 0.7.1]
- Django [required: >=2.2,<5, installed: 3.2.16]
--
drf-spectacular==0.25.1
- Django [required: >=2.2, installed: 3.2.16]
Upgrade to Django 4.1.5
Based upon this pip dependency graph, upgrading from Django 3.2 to 4.1 should not be too troublesome from a deep perspective