[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):

• 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.5 to address security vulnerability SNYK-PYTHON-WERKZEUG-14908843, as identified by Snyk's automated security scanning.

Changes:

• Upgraded Werkzeug dependency from 2.2.3 to 3.1.5 in local development requirements

---

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

[Copilot]

This is a major version upgrade from Werkzeug 2.2.3 to 3.1.5. Werkzeug 3.x introduced several breaking changes that may affect compatibility with django-extensions 3.2.1 (currently used in this project). The django-extensions package uses Werkzeug for its runserver_plus command, which is actively used in the local development environment (see compose/local/django/start).

Before merging this PR, it's recommended to:

1. Test the local development environment thoroughly, especially the runserver_plus command
2. Consider upgrading django-extensions to a version that officially supports Werkzeug 3.x
3. Verify that all development server features (debugging, auto-reload, etc.) work as expected

If compatibility issues arise, you may need to either pin Werkzeug to a 2.x version that addresses the security vulnerability, or upgrade django-extensions first.