[Snyk] Security upgrade werkzeug from 2.2.3 to 3.1.5

[robertatakenaka]

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

Snyk changed the following file(s):

• proj/requirements.txt

⚠️ Warning

Flask 2.2.5 requires Werkzeug, which is not installed.
Flask-JWT-Extended 4.6.0 requires Werkzeug, which is not installed.
celery 5.3.0 requires kombu, 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.

[Copilot]

Pull request overview

This PR upgrades Werkzeug from version 2.2.3 to 3.1.5 to fix a security vulnerability (SNYK-PYTHON-WERKZEUG-14908843). This is a major version upgrade that addresses critical security issues but introduces breaking changes.

Changes:

• Added Werkzeug version constraint (>=3.1.5) to requirements.txt to resolve security vulnerability

---

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

[Copilot]

This upgrade from Werkzeug 2.2.3 to 3.1.5 is a major version change (2.x to 3.x) that includes breaking changes. The warning messages in the PR description indicate that Flask 2.2.5 and Flask-JWT-Extended 4.6.0 both require Werkzeug but may not be compatible with version 3.x. To ensure compatibility, you should:

1. Pin Flask to a version that supports Werkzeug 3.x (Flask >= 3.0.0 supports Werkzeug 3.x)
2. Pin Flask-JWT-Extended to a compatible version (check compatibility with both Flask 3.x and Werkzeug 3.x)
3. Test all Flask-related functionality thoroughly after this upgrade

Without explicit version constraints for Flask and its extensions, pip may install incompatible versions that could break the application at runtime.

[Copilot]

The use of '>=' operator for Werkzeug allows future versions beyond 3.1.5, which could introduce additional breaking changes or compatibility issues. For critical security fixes, consider using a more restrictive constraint like 'werkzeug>=3.1.5,<4.0.0' to stay within the 3.x series while still receiving patch updates, or pin to a specific version range to avoid unexpected breaking changes in future major versions.

Suggested change

	werkzeug>=3.1.5 # not directly required, pinned by Snyk to avoid a vulnerability
	werkzeug>=3.1.5,<4.0.0 # not directly required, pinned by Snyk to avoid a vulnerability