[Snyk] Security upgrade urllib3 from 2.0.7 to 2.5.0

[paaschdigital]

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

Snyk changed the following file(s):

• requires-testing.txt

⚠️ Warning

equests 2.31.0 requires urllib3, 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:

🦉 Open Redirect

[gemini-code-assist]

Summary of Changes

Hello @paaschdigital, 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, aims to enhance the project's security posture by upgrading the urllib3 library to a more secure version. It addresses identified vulnerabilities by explicitly pinning urllib3 in the requires-testing.txt file, ensuring that a known secure version is used for testing dependencies.

Highlights

• Security Upgrade: Upgrades the urllib3 library from version 2.0.7 to 2.5.0 to resolve two reported security vulnerabilities (SNYK-PYTHON-URLLIB3-10390193 and SNYK-PYTHON-URLLIB3-10390194).
• Dependency Pinning: Explicitly adds urllib3>=2.5.0 to requires-testing.txt. This change addresses a previous implicit dependency (as noted by Snyk, requests requires urllib3 but it wasn't listed), ensuring the project directly controls the urllib3 version for security.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 urllib3 to version 2.5.0 to fix security vulnerabilities.

However, the proposed change introduces a critical dependency conflict. The new version of urllib3 is incompatible with older versions of the requests library that are still allowed by the current dependency specification (requests>=2.21.0). This will break the installation of testing dependencies.

My review includes a comment on the added line in requires-testing.txt explaining the issue and suggesting a fix, which involves updating the requests version constraint as well.

[gemini-code-assist]

This upgrade of urllib3 to version 2.5.0 will cause dependency conflicts and break the installation of testing requirements.

The requests library versions prior to 2.32.0 are not compatible with urllib3>=2.0. The current requirement in this file is requests[security]>=2.21.0 (on line 7), which allows incompatible versions of requests (e.g., 2.31.0 as hinted at in the PR description) to be chosen by pip.

When pip tries to resolve dependencies, it will face a conflict:

• requests<2.32.0 requires urllib3<2.0
• This PR adds a requirement for urllib3>=2.5.0

To fix this, the requests dependency on line 7 must also be updated to a version that supports urllib3 v2. I recommend updating line 7 to:

requests[security]>=2.32.0

This will ensure a compatible version of requests is installed along with the upgraded urllib3.