[Snyk] Security upgrade django from 2.2.26 to 4.2.26

[MaKyOtOx]

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

Upgrades Django from 2.2.26 to 4.2.26 in requirements.txt.

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

[cursor]

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

Your free Bugbot reviews will reset on November 19

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: New Django, old dependencies: compatibility breakdown.

Upgrading Django from 2.2.26 to 4.2.26 without updating dependent packages creates compatibility issues. Several pinned dependencies (django-rest-swagger==2.2.0, django-datetime-widget==0.9.3, django-extensions==2.1.9, django-cursor-pagination==0.1.4, django-debug-toolbar==3.2.2) were designed for Django 2.x and are incompatible with Django 4.2, which will cause runtime failures when these packages are imported or used.