[Snyk] Security upgrade werkzeug from 2.1.2 to 3.1.4

[q1blue]

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

Snyk changed the following file(s):

• requirements-minimal.txt

⚠️ Warning

moto 4.0.1 requires werkzeug, 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 Werkzeug to 3.1.4 in requirements-minimal.txt to fix a security vulnerability, with a warning about moto dependency.

• Dependency Upgrade:
  • Upgrade Werkzeug from 2.1.2 to 3.1.4 in requirements-minimal.txt to fix a security vulnerability.
• Warnings:
  • moto 4.0.1 requires werkzeug, which may not be installed after the upgrade.

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

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[changeset-bot]

⚠️ No Changeset found

Latest commit: 07b02ce

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

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
buildbot	Error			Dec 1, 2025 4:45am
csb-b6x6kw	Ready	Preview	Comment	Dec 1, 2025 4:45am

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 07b02ce in 29 seconds. Click for details.

• Reviewed 13 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-minimal.txt:94

• Draft comment:
  Werkzeug upgraded from 2.1.2 to 3.1.4 to address security vulnerabilities. Ensure that no parts of the application depend on deprecated or changed APIs in Werkzeug 3.x.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is about a dependency upgrade, specifically Werkzeug from version 2.1.2 to 3.1.4. It advises ensuring that no parts of the application depend on deprecated or changed APIs in the new version. This falls under the rule of not commenting on dependency changes or asking the author to ensure compatibility, which is not allowed.

Workflow ID: wflow_zyKgni6NsSyUanO6

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