[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-extensions 3.2.1 requires Django, which is not installed.
django-debug-toolbar 3.8.1 requires django, which is not installed.
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 addresses a security vulnerability by pinning Django to version 4.2.26 or higher in production requirements, as recommended by Snyk.

• Uncomments the elastic-apm dependency
• Adds a security pin for Django to version >=4.2.26

---

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

[Copilot]

The version constraint django>=4.2.26 conflicts with the pinned version in base.txt which specifies django==4.1.6. Since production.txt includes base.txt (line 3), this creates a dependency conflict. The base Django version should be upgraded to at least 4.2.26, or this pin should specify a compatible constraint like django>=4.2.26,<5.0 if the project needs to stay within Django 4.x series.

Suggested change

	elastic-apm==6.15.1
	django>=4.2.26 # not directly required, pinned by Snyk to avoid a vulnerability
	elastic-apm==6.15.1