[Snyk] Security upgrade django from 3.2.25 to 4.2.28

[Dustin4444]

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

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

xml2rfc 3.25.0 requires platformdirs, which is not installed.
xml2rfc 3.25.0 requires configargparse, which is not installed.
xml2rfc 3.25.0 requires google-i18n-address, which is not installed.
xml2rfc 3.25.0 requires intervaltree, which is not installed.
xml2rfc 3.25.0 requires jinja2, which is not installed.
xml2rfc 3.25.0 requires pycountry, which is not installed.
scout-apm 2.26.1 has requirement urllib3[secure]<2; python_version >= "3.5", but you have urllib3 2.0.7.
pydantic-settings 2.0.3 has requirement pydantic>=2.0.1, but you have pydantic 1.10.26.
celery 5.3.0 requires kombu, 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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
datatracker	Error		Feb 11, 2026 5:42am

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-e7e0325466a793975eaa36d9997fa3a5

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, addresses a critical security vulnerability by upgrading the Django framework. The primary goal is to transition the project's Django dependency from version 3.2.25 to 4.2.28, ensuring enhanced security. This change is implemented by modifying the version constraint for Django within the requirements.txt file.

Highlights

• Django Security Upgrade: Upgraded the Django dependency from version 3.2.25 to 4.2.28 to address a security vulnerability identified by Snyk. The requirements.txt file was updated to reflect this by changing the Django version constraint.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• requirements.txt
  • Updated the Django dependency constraint from Django>4.2,<5 to Django>4.2.28 to ensure a secure version of Django 4.x is used.

Activity

• This pull request was automatically generated by Snyk to address a security vulnerability.
• No human activity or reviews have been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to upgrade Django to version 4.2.28 to address security vulnerabilities. The change modifies the version specifier in requirements.txt. However, the new specifier >4.2.28 is incorrect as it excludes version 4.2.28 itself. I've suggested a correction to ensure the intended version is installed while maintaining the existing upper bound to prevent compatibility issues with future major Django releases.

[gemini-code-assist]

The version specifier >4.2.28 for Django excludes version 4.2.28 itself. As this PR aims to fix a security vulnerability by upgrading to 4.2.28, this specifier will not install the intended version. Instead, it will look for a version strictly greater than 4.2.28.

To ensure the correct version is installed, please change the specifier to >=4.2.28. It is also advisable to retain the upper bound <5 from the previous constraint to prevent accidentally pulling in Django 5, for which the project does not seem to be ready yet.

Django>=4.2.28,<5