[Snyk] Security upgrade werkzeug from 2.2.3 to 3.1.4

[robertatakenaka]

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

Snyk changed the following file(s):

• requirements/local.txt

⚠️ Warning

flake8 4.0.1 has requirement importlib-metadata<4.3; python_version < "3.8", but you have importlib-metadata 6.7.0.

---

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.

[Copilot]

Pull request overview

This PR upgrades Werkzeug from version 2.2.3 to 3.1.4 in the local development requirements to address security vulnerability SNYK-PYTHON-WERKZEUG-14151620. However, this major version upgrade introduces potential compatibility risks with existing dependencies, particularly Flower 1.2.0 (Celery monitoring tool) which depends on Werkzeug through Flask.

Key Changes:

• Upgraded Werkzeug to 3.1.4 in local.txt to fix a security vulnerability
• Major version jump (2.x → 3.x) introduces breaking changes that may affect transitive dependencies

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Upgrading Werkzeug from 2.2.3 to 3.1.4 may cause compatibility issues with Flower 1.2.0 (defined in base.txt). Werkzeug 3.x introduced breaking changes, and Flower 1.2.0 (released in 2022) was built for Werkzeug 2.x. This could break the Flower monitoring dashboard used in the celeryworker service.

Consider either:

1. Testing Flower extensively after this upgrade to ensure it still works
2. Upgrading Flower to version 2.0.0 or later (which supports Werkzeug 3.x) alongside this change
3. Pinning Werkzeug to a patched 2.x version (e.g., 2.3.8) that addresses the security vulnerability without breaking compatibility

Suggested change

	Werkzeug==3.1.4 # https://github.com/pallets/werkzeug
	Werkzeug==2.3.8 # https://github.com/pallets/werkzeug