Skip to content

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

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

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

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
3 changes: 2 additions & 1 deletion requirements/local.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,4 +40,5 @@ tornado>=6.3.3 # not directly required, pinned by Snyk to avoid a vulnerability

django-test-migrations==1.3.0

django-silk==5.3.2
django-silk==5.3.2
django>=4.2.26 # not directly required, pinned by Snyk to avoid a vulnerability
Comment on lines +43 to +44
Copy link

Copilot AI Nov 9, 2025

Choose a reason for hiding this comment

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

This requirement conflicts with django==5.2.7 specified in requirements/base.txt. Since local.txt includes base.txt, this creates an impossible constraint. If a security update is needed, the version should be updated in base.txt instead, or this line should specify a compatible version range like django>=5.2.7.

Suggested change
django-silk==5.3.2
django>=4.2.26 # not directly required, pinned by Snyk to avoid a vulnerability
django-silk==5.3.2

Copilot uses AI. Check for mistakes.
Loading