[Snyk] Security upgrade django from 3.2.25 to 4.2.28

[robertatakenaka]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements/production.txt

⚠️ Warning

django-anymail 11.1 requires django, which is not installed.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 SQL Injection

[Copilot]

Pull request overview

This PR was created by Snyk to address security vulnerability SNYK-PYTHON-DJANGO-15183335 by upgrading Django from 3.2.25 to 4.2.28. However, there is a critical issue: the codebase already has Django 5.2.7 pinned in requirements/base.txt, which supersedes the proposed Django 4.2.28 constraint.

Changes:

• Adds django>=4.2.28 to the SECURITY UPDATES section in requirements/production.txt

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This change conflicts with the existing Django version pinned in requirements/base.txt. The base.txt file specifies django==5.2.7 (line 19), but this PR adds django>=4.2.28 to production.txt. Since production.txt includes base.txt via "-r base.txt", Django 5.2.7 is already installed, making this additional constraint unnecessary and potentially confusing.

The comment "not directly required" is also misleading because Django is directly required in base.txt. If the intent is to ensure Django is at least version 4.2.28 for security reasons, that requirement is already satisfied by the existing django==5.2.7 constraint. This line should be removed.

Suggested change

	setuptools>=68.2.2 # not directly required, pinned by Snyk to avoid a vulnerability
	django>=4.2.28 # not directly required, pinned by Snyk to avoid a vulnerability
	setuptools>=68.2.2 # not directly required, pinned by Snyk to avoid a vulnerability

[Copilot]

The PR description mentions upgrading from Django 3.2.25 to 4.2.28, but the codebase currently has django==5.2.7 specified in requirements/base.txt (line 19). This discrepancy suggests the PR description may be outdated or incorrect. Django 5.2.7 was released after my knowledge cutoff (January 2025), so I cannot verify its validity, but if it's a legitimate version, it already satisfies any security requirements for Django >= 4.2.28. Please verify that the current Django version (5.2.7) addresses the security vulnerability SNYK-PYTHON-DJANGO-15183335 mentioned in the PR description.