[Snyk] Security upgrade werkzeug from 2.0.1 to 3.1.4

[MaKyOtOx]

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

Snyk changed the following file(s):

• requirements.macos.txt

---

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.

---

Note

Upgrades Werkzeug in requirements.macos.txt from 2.0.1 to 3.1.4.

^{Written by Cursor Bugbot for commit 16b600a. This will update automatically on new commits. Configure here.}

[cursor]

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on December 19

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Werkzeug version inconsistency between requirements files

This security fix updates Werkzeug to 3.1.4 only in requirements.macos.txt, while requirements.txt still specifies version 2.0.1. This version inconsistency between requirements files means macOS environments will run Werkzeug 3.x while other environments run 2.x. Since this is a major version upgrade with breaking API changes, this could cause environment-specific failures where code works on macOS but breaks elsewhere. Additionally, non-macOS deployments remain on the vulnerable version, defeating the security purpose of this upgrade.