Skip to content

[Snyk] Security upgrade django from 3.2.25 to 4.2.26 #261

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
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade django from 3.2.25 to 4.2.26 #261

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
@@ -1,4 +1,4 @@
Django>=4.0,<6
Django>=4.2.26
Copy link

@cursor cursor bot Nov 12, 2025

Choose a reason for hiding this comment

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

Bug: Untested Django versions risk dependency conflicts.

The Django version constraint changed from >=4.0,<6 to >=4.2.26, removing the upper bound. This allows Django 6.x (and beyond) to be installed, but django-phonenumber-field==6.1.0 on line 4 may not support Django 6.x. The CI workflow only tests up to Django 5.0, and Django 6.x is still under development. This creates a risk of installing incompatible package versions that haven't been tested together.

Fix in Cursor Fix in Web

Sphinx>=1.2.0
phonenumbers>=7.0.2
django-phonenumber-field==6.1.0
Expand Down
Loading