[Snyk] Security upgrade urllib3 from 2.7.0 to 2.8.0

[snyk-io-us]

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

Snyk changed the following file(s):

• executor/requirements.txt

⚠️ Warning

lightbeam 0.1.12 requires requests, which is not installed.
lightbeam 0.1.12 requires pyyaml, which is not installed.
lightbeam 0.1.12 has requirement setuptools>=44.0.0, but you have setuptools 40.5.0.
jinja2 3.1.6 requires MarkupSafe, which is not installed.
earthmover 0.4.10 requires pandas, which is not installed.
earthmover 0.4.10 requires requests, which is not installed.
earthmover 0.4.10 requires dask, which is not installed.
earthmover 0.4.10 requires networkx, which is not installed.
earthmover 0.4.10 has requirement setuptools>=44.0.0, but you have setuptools 40.5.0.

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:

🦉 Allocation of Resources Without Limits or Throttling

[snyk-io-us]

This minor version upgrade includes several security fixes and a significant behavioral change related to HTTPS proxies.

Key Changes:

• HTTPS Proxy TLS Configuration: A fix was implemented (GHSA-8988-9cw3-xx77) that changes how TLS settings are applied to HTTPS proxies. Previously, destination TLS settings could incorrectly apply to the proxy connection. Now, proxy-specific TLS configurations must be set explicitly using parameters like proxy_ssl_context, proxy_assert_hostname, or proxy_assert_fingerprint.
• Security Fixes: This release addresses multiple security vulnerabilities, including potential unbounded memory buffering and an infinite loop in chunked deflate streaming.
• Deprecation: Using an empty collection for the allowed_methods option in Retry is now deprecated.

Action Required:
If you use urllib3 with an HTTPS proxy, you must verify your configuration. Ensure that any custom TLS settings for the proxy (like CA certificates or client certificates) are passed via the correct proxy-specific parameters, as they will no longer inherit from the destination's settings.

Source: urllib3 2.8.0 Release Notes

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

[amazon-inspector-ohio]

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

[snyk-io-us]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[amazon-inspector-ohio]

✅ I finished the code review, and didn't find any security or code quality issues.