[Snyk] Security upgrade urllib3 from 1.26.18 to 2.6.0 #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):
requirements-dev.txtThis major upgrade to
urllib3v2 introduces significant breaking changes. Developer action is required to ensure compatibility.Key Changes:
HTTPResponse.getheaders()andHTTPResponse.getheader(), have been removed in v2.6.0.urllib3[secure]extra has been removed.Source: v2.0 Migration Guide
Recommendation: Ensure your environment uses Python 3.9+ and OpenSSL 1.1.1+. Review code for usage of removed APIs and test connectivity against all target endpoints, especially those with older TLS configurations.
Important
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
👩💻 Set who automatically gets assigned
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling