[Snyk] Security upgrade django from 3.2.25 to 4.2.27

[rdegges]

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

Snyk changed the following file(s):

• requirements.txt

---

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

---

Note

Updates Django requirement to ">=4.2.27" (removes "<6" upper bound) in requirements.txt.

^{Written by Cursor Bugbot for commit 43c6e49. This will update automatically on new commits. Configure here.}

[rdegges]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[cursor]

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on January 1

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Django version upper bound constraint removed unexpectedly

The Django version constraint changed from Django>=4.0,<6 to Django>=4.2.27, which removes the upper bound constraint (<6). This allows any future Django version (including potential 6.x releases) to be installed, which could introduce breaking changes. The original constraint deliberately limited Django to versions below 6. Additionally, the minimum version 4.2.27 conflicts with the CI matrix which tests Django 4.0 and 4.1 - this creates an inconsistency where declared supported versions don't match the requirements.