[Snyk] Security upgrade django from 1.11.29 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-dev.txt

⚠️ Warning

django-extensions 3.2.3 requires Django, which is not installed.
django-debug-toolbar 3.8.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

Updates the development dependency list to address a Snyk-reported Django vulnerability by introducing an explicit Django version constraint in dev requirements.

Changes:

• Add django>=4.2.28 to requirements-dev.txt with a Snyk-generated comment.

---

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

[Copilot]

Dependency name casing is inconsistent with the rest of this repo: requirements.txt uses Django (capitalized) while this adds django. Pip treats names case-insensitively, but keeping casing consistent reduces diff churn and tooling inconsistencies (e.g., grep/audit scripts).

[Copilot]

This change doesn’t match the PR description (“upgrade django from 1.11.29 to 4.2.28” to fix a vulnerability): the repo’s declared Django requirement is currently Django<1.5 (requirements.txt:1), and the new constraint is only added to requirements-dev.txt. If the vulnerability is relevant to runtime, it won’t be addressed by a dev-only dependency; if it’s dev-only, the project’s Django constraint/version should be clarified so dependency scanning results are consistent.