Skip to content

[Snyk] Security upgrade django from 3.1.8 to 4.2.26 #169

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

[Snyk] Security upgrade django from 3.1.8 to 4.2.26 #169

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 @@ -74,7 +74,7 @@ git+https://github.com/zapier/django-rest-hooks.git@v1.6.0
# via -r requirements.in
django-statsd==2.5.2
# via -r requirements.in
django==3.1.8
django==4.2.26

@cursor cursor Bot Nov 8, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: Dependency Conflict Undoes Security Upgrade

The Django upgrade in requirements.txt is inconsistent with requirements.in, which still pins Django==3.1.8. Since requirements.txt is auto-generated by pip-compile requirements.in, running the compilation command will revert Django back to 3.1.8, undoing the security fix. The source file requirements.in must also be updated for the upgrade to persist.

Fix in Cursor Fix in Web

# via
# -r requirements.in
# django-axes
Expand Down