[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• requirements-ci.txt

⚠️ Warning

esponses 0.20.0 requires urllib3, which is not installed.
requests 2.27.1 requires urllib3, which is not installed.
moto 2.1.0 requires werkzeug, which is not installed.
flake8 4.0.1 has requirement importlib-metadata<4.3; python_version < "3.8", but you have importlib-metadata 6.7.0.
buildbot 4.3.0 requires autobahn, which is not installed.
buildbot 4.3.0 has requirement unidiff>=0.7.5, but you have unidiff 0.7.3.
botocore 1.21.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 and Werkzeug in requirements-ci.txt to fix vulnerabilities.

• Dependencies:
  • Upgrade urllib3 from 1.26.9 to 2.6.3 in requirements-ci.txt.
  • Upgrade Werkzeug from 2.1.2 to 3.1.5 in requirements-ci.txt.

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

[vercel]

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

Project	Deployment	Review	Updated (UTC)
buildbot	Error		Jan 15, 2026 10:01am
csb-b6x6kw	Ready	Preview, Comment	Jan 15, 2026 10:01am

[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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6d7d913

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 6d7d913 in 1 minute and 0 seconds. Click for details.

• Reviewed 17 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 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-ci.txt:108

• Draft comment:
  Upgrading urllib3 from 1.26.9 to 2.6.3 addresses vulnerabilities, but requests==2.27.1 typically requires urllib3 < 1.27. Please verify that the new version is compatible with its consumers.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is about a dependency change, specifically the upgrade of urllib3, and it mentions a potential compatibility issue with requests. However, it asks the PR author to verify compatibility, which violates the rule against asking for verification or confirmation. Therefore, this comment should not be approved.

2. requirements-ci.txt:111

• Draft comment:
  Upgrading Werkzeug from 2.1.2 to 3.1.5 fixes vulnerabilities, but the jump to a new major version could break dependent packages (e.g., moto==2.1.0). Confirm compatibility with all consumers.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is about a dependency change, specifically upgrading the Werkzeug library. It mentions potential compatibility issues with dependent packages, which is a valid concern. However, it asks the PR author to confirm compatibility, which violates the rule against asking for confirmation or verification. Therefore, this comment should not be approved.

Workflow ID: wflow_RO86YZFzwCnpjFGZ

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