Skip to content

build(deps): bump the pip group across 1 directory with 3 updates #11032

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

Closed
wants to merge 1 commit into from
Closed

build(deps): bump the pip group across 1 directory with 3 updates #11032

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
6 changes: 3 additions & 3 deletions lib/wasm-micro-runtime-WAMR-2.4.1/tests/fuzz/wasm-mutator-fuzz/server/requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
Flask==1.1.4
Flask==2.2.5
Flask_SQLAlchemy==2.5.1
flask-migrate==2.7.0
flask-script==2.0.6
Comment on lines +1 to 4
Copy link

Choose a reason for hiding this comment

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

P1 Badge Upgrade breaks flask-script CLI compatibility

Raising Flask to 2.2.5 (and Werkzeug to 3.0.6) while still pinning flask-script==2.0.6 makes the management script unusable. flask_script depends on the removed flask._compat module and fails to import under Flask ≥2.0, so python app/manager.py will crash before any migrations or admin commands run. Either keep Flask below 2.0 or replace flask-script with Flask’s built-in CLI / Flask-Migrate integration when upgrading these core libraries.

Useful? React with 👍 / 👎.

flask-cors==3.0.10
flask-cors==6.0.0
flask-caching==2.0.0
werkzeug==1.0.1
werkzeug==3.0.6
markupsafe==2.0.1
flask-apscheduler==1.12.4
psutil==5.9.2
Expand Down
Loading