Skip to content

[Snyk] Security upgrade werkzeug from 0.16.0 to 3.1.4 #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NewthingAde wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade werkzeug from 0.16.0 to 3.1.4 #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,5 +10,5 @@ pytz==2019.3
scikit-learn==0.20.3
scipy==1.3.1
six==1.12.0
Werkzeug==0.16.0
Werkzeug==3.1.4
Copy link

@cursor cursor bot Nov 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Werkzeug 3.x incompatible with Flask 1.0.2

Upgrading Werkzeug from 0.16.0 to 3.1.4 while keeping Flask==1.0.2 creates an incompatible dependency combination. Flask 1.0.2 was designed for Werkzeug 0.x and relies on internal APIs that have been removed or renamed in Werkzeug 3.x. This will cause runtime import errors when Flask attempts to use Werkzeug modules that no longer exist. The PR description's warning "Flask 1.0.2 requires Werkzeug, which is not installed" indicates this conflict. Flask needs to be upgraded to a compatible version (2.x or 3.x) alongside this Werkzeug upgrade.

Fix in Cursor Fix in Web

pylint==2.4.4