[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/local.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 local development requirements in response to a Snyk-reported Django vulnerability, aiming to ensure an upgraded Django version is installed when using requirements/local.txt.

Changes:

• Normalizes the django-silk requirement line formatting.
• Adds a new django>=4.2.28 requirement in requirements/local.txt.

---

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

[Copilot]

requirements/local.txt includes -r base.txt, and requirements/base.txt already pins django==5.2.7 (base.txt:19). Adding django>=4.2.28 here is redundant and introduces a second (less specific) constraint, which also doesn’t match the PR title/description claiming an upgrade from 3.2.25. Suggest removing this line and, if a Django security bump is needed, adjusting the pinned version in requirements/base.txt instead (or ensure Snyk is scanning the right requirements file).