[Snyk] Security upgrade django from 3.2.25 to 4.2.26

[robertatakenaka]

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

Snyk changed the following file(s):

• requirements/production.txt

⚠️ Warning

django-anymail 10.3 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 upgrades Django from version 3.2.25 to 4.2.26 to address 2 security vulnerabilities (SQL Injection and another vulnerability) identified by Snyk.

Key Changes:

• Django version upgraded from 3.2.25 to 4.2.26
• Addition of explicit Django dependency constraint in production requirements

---

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

[Copilot]

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]

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