[Snyk] Security upgrade requests from 2.31.0 to 2.32.4

[paaschdigital]

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

Snyk changed the following file(s):

• requires-ci.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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[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 focuses on improving the project's security by applying an automated dependency upgrade. It addresses a known vulnerability in the requests Python library, ensuring that the project's continuous integration environment uses a more secure version of this critical dependency.

Highlights

• Security Upgrade: This pull request, automatically generated by Snyk, upgrades the requests Python package from version 2.31.0 to 2.32.4. This upgrade specifically addresses a detected vulnerability (SNYK-PYTHON-REQUESTS-10305723) in the requests dependency.

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 Snyk pull request upgrades the requests library to version >=2.32.4 within the requires-ci.txt file to address security vulnerability SNYK-PYTHON-REQUESTS-10305723.

The primary feedback is a strong recommendation to also apply this version constraint (requests>=2.32.4) to requires-install.txt. This is because requests is a direct, currently unpinned dependency in requires-install.txt, and pinning it there is essential to ensure the vulnerability is fixed for the core distributable package and all its users, not just within the CI environment.

Additionally, a suggestion has been made to improve the clarity of the comment on the newly added line in requires-ci.txt to more accurately reflect that requests is a project dependency.

[gemini-code-assist]

This PR pins requests to version >=2.32.4 in requires-ci.txt to address Snyk vulnerability SNYK-PYTHON-REQUESTS-10305723. While this secures the CI environment, there are important considerations for comprehensive protection:

1. Core Package Vulnerability: requests is a direct, unpinned dependency in requires-install.txt (line 9). To ensure the vulnerability is remediated for the actual distributable package and all its users, it is crucial to also add the constraint requests>=2.32.4 to requires-install.txt. Relying solely on this pin in requires-ci.txt might not protect the package if pip resolves requests to an older, vulnerable version during a standard installation (e.g., pip install .).

2. Comment Clarity: The current comment # not directly required... is potentially misleading. Since requests is a direct dependency of the project (via requires-install.txt), it is directly required. Snyk likely means it wasn't a pre-existing top-level entry in this specific requires-ci.txt file or is a transitive dependency within the CI scope that needed an explicit pin. A more accurate comment would improve clarity.

Recommendation:
Please prioritize updating requires-install.txt to include requests>=2.32.4. For the current line in requires-ci.txt, the suggested comment below offers improved accuracy, especially if the pin is also added to requires-install.txt.

requests>=2.32.4 # Project dependency, pinned by Snyk to >=2.32.4 in CI to fix SNYK-PYTHON-REQUESTS-10305723