[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 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 attempts to upgrade Django from version 3.2.25 to 4.2.28 to address a SQL Injection vulnerability (SNYK-PYTHON-DJANGO-15183335). However, the PR is based on incorrect dependency information - the project already uses Django 5.2.3 as specified in requirements/base.txt, which is significantly newer than the target version 4.2.28.

Changes:

• Adds django>=4.2.28 to requirements/production.txt

[Copilot]

This change creates a conflicting Django version requirement. The base.txt file (which is included via -r base.txt on line 3) already specifies django==5.2.3. Adding django>=4.2.28 to production.txt will cause a dependency conflict since pip cannot satisfy both django==5.2.3 and django>=4.2.28 simultaneously (even though 5.2.3 is greater than 4.2.28, the exact version pin in base.txt takes precedence and conflicts).

The project is already using Django 5.2.3, which is significantly newer than 4.2.28 and should already include the security fixes that this PR aims to address. This PR appears to be based on outdated dependency information and is not needed.

Suggested change

	elastic-apm==6.21.4.post8347027212
	django>=4.2.28 # not directly required, pinned by Snyk to avoid a vulnerability
	elastic-apm==6.21.4.post8347027212

[Copilot]

The PR description states this upgrades Django from 3.2.25 to 4.2.28, but the codebase already has Django 5.2.3 specified in requirements/base.txt. This indicates that the Snyk scan may have been performed on outdated or incorrect dependency information. The project does not actually use Django 3.2.25, so this security upgrade is not applicable to the current state of the codebase.