[Snyk] Security upgrade urllib3 from 2.5.0 to 2.7.0

[snykbotzup]

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

Snyk changed the following file(s):

• requirements.txt

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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.

[snykbotzup]

This upgrade of urllib3 is high risk due to the removal of a deprecated method that is known to affect downstream libraries.

Breaking Changes:

• HTTPResponse.getheaders() Removed: Version 2.6.0 removed the getheaders() method, which was deprecated in v2.0.0. It has been replaced by the .headers property. Code that still uses getheaders() will break. [7, 10] This change is known to have caused issues with packages like the kubernetes-client. [10]
• Python 3.9 Support Dropped: Version 2.7.0 removed support for the end-of-life Python 3.9. [5]
• Custom Decompressor API: Version 2.6.0 changed the API for custom content decoders. If you implement custom decompressors, they will need to be updated. [1, 7]

Recommendation:
Before upgrading, search your codebase for any usage of response.getheaders() and replace it with response.headers. Verify that your environment is running Python 3.10 or newer. If you use custom content decoders, review the urllib3 changelog to adapt to the new API.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.