Skip to content

[Snyk] Security upgrade django from 2.2.26 to 4.2.26 #442

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MaKyOtOx wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade django from 2.2.26 to 4.2.26 #442

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ certifi==2017.4.17
chardet==3.0.4
coreapi==2.3.3
coreschema==0.0.4
Django==2.2.26
Django==4.2.26
Copy link
Copy Markdown

@cursor cursor Bot Nov 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: New Django, old dependencies: compatibility breakdown.

Upgrading Django from 2.2.26 to 4.2.26 without updating dependent packages creates compatibility issues. Several pinned dependencies (django-rest-swagger==2.2.0, django-datetime-widget==0.9.3, django-extensions==2.1.9, django-cursor-pagination==0.1.4, django-debug-toolbar==3.2.2) were designed for Django 2.x and are incompatible with Django 4.2, which will cause runtime failures when these packages are imported or used.

Fix in Cursor Fix in Web

#django-celery-beat==1.1.1
django-celery-beat==2.0.0
django-celery-results==2.0.1
Expand Down
Loading