Skip to content

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

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 #771

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/production.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,5 @@ setuptools>=68.2.2 # not directly required, pinned by Snyk to avoid a vulnerabil

# Elastic-APM # https://pypi.org/project/elastic-apm/
# ------------------------------------------------------------------------------
elastic-apm==6.21.4.post8347027212
elastic-apm==6.21.4.post8347027212
django>=4.2.26 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link

Copilot AI Nov 8, 2025

Choose a reason for hiding this comment

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

The comment 'not directly required' is misleading since Django is clearly a core framework dependency, not a transitive one. Consider updating the comment to accurately reflect that this is pinning the Django version for security reasons, e.g., '# pinned by Snyk to address security vulnerabilities'.

Suggested change
django>=4.2.26 # not directly required, pinned by Snyk to avoid a vulnerability
django>=4.2.26 # pinned by Snyk to address security vulnerabilities

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Nov 8, 2025

Choose a reason for hiding this comment

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

Using '>=' allows any version 4.2.26 or higher, which could introduce breaking changes in future major versions (e.g., 5.x). Consider using a more restrictive version constraint like 'django>=4.2.26,<5.0' to prevent unintended upgrades while still receiving 4.x security patches.

Suggested change
django>=4.2.26 # not directly required, pinned by Snyk to avoid a vulnerability
django>=4.2.26,<5.0 # not directly required, pinned by Snyk to avoid a vulnerability

Copilot uses AI. Check for mistakes.