[Snyk] Security upgrade urllib3 from 1.26.20 to 2.6.3

[q1blue]

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

Snyk changed the following file(s):

• requirements-master-docker-extras.txt

⚠️ Warning

twisted 23.8.0 requires zope-interface, which is not installed.
requests 2.27.1 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:

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

---

Important

Upgrade urllib3 to >=2.6.3 in requirements-master-docker-extras.txt to fix a security vulnerability.

• Dependency Upgrade:
  • Upgrade urllib3 to >=2.6.3 in requirements-master-docker-extras.txt to fix a security vulnerability.
• Warnings:
  • twisted 23.8.0 requires zope-interface, which is not installed.
  • requests 2.27.1 requires urllib3, which is not installed.

^{This description was created by for 01b4ce7. You can customize this summary. It will automatically update as commits are pushed.}

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
buildbot	Error		Jan 13, 2026 11:26pm
csb-b6x6kw	Ready	Preview, Comment	Jan 13, 2026 11:26pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 01b4ce7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 01b4ce7 in 1 minute and 34 seconds. Click for details.

• Reviewed 9 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. requirements-master-docker-extras.txt:5

• Draft comment:
  Warning: urllib3>=2.6.3 on L5 conflicts with requests==2.27.1, which requires urllib3<1.27. Upgrading urllib3 to 2.x may break compatibility with requests. Consider updating requests to a version that supports urllib3 2.x (e.g. >=2.28) or adjust the urllib3 version range accordingly.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% This comment is about a change in the diff (the addition of urllib3>=2.6.3). It identifies a specific technical issue: a dependency conflict between two packages. The comment is actionable and provides concrete suggestions. However, I need to consider: (1) Is this something that would be caught by the build/pip install? Yes, pip would likely fail or warn about this conflict. (2) The rules say "Do NOT comment on anything that would be obviously caught by the build". This dependency conflict would be caught when trying to install these requirements. (3) But the comment does provide useful context about which versions would work together, which might not be immediately obvious from a pip error message. While this is a real dependency conflict, pip will immediately fail when trying to install these requirements together, making this an issue that would be "obviously caught by the build". The rules explicitly state not to comment on such issues. Additionally, the PR author may have already tested this or may be aware of the conflict. Although pip will catch this, the comment provides specific actionable guidance on how to resolve the conflict (upgrade requests to >=2.28), which goes beyond what a simple pip error would tell you. This could save the developer time. However, the rules are clear about not commenting on build-time issues, and dependency conflicts are quintessentially build-time issues. This comment should be deleted because it identifies a dependency conflict that would be immediately caught by pip during installation, which falls under "anything that would be obviously caught by the build" per the rules. While the suggestions are helpful, the rules prioritize not commenting on build-time issues.

Workflow ID: wflow_52AOCFsHfUTjueSX

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}