-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Security upgrade werkzeug from 2.2.3 to 3.1.5 #11
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -13,3 +13,4 @@ apispec-webframeworks | |||||
| tox | ||||||
| celery[redis]>=5.0.0 | ||||||
| gunicorn | ||||||
| werkzeug>=3.1.5 # not directly required, pinned by Snyk to avoid a vulnerability | ||||||
|
||||||
| 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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:
Without explicit version constraints for Flask and its extensions, pip may install incompatible versions that could break the application at runtime.