Skip to content

Conversation

@marcstern14
Copy link

@marcstern14 marcstern14 commented Nov 27, 2024

werkzeug>=3.1 is compatible within the set flask boundaries. Removing the boundaries for werkzeug would allow for more flexible installations on deployed apps without triggering vulnerabilities.

`werkzeug>=3.1` is compatible within the set flask boundaries. Removing the boundaries for `werkzeug` would allow for more flexible installations on deployed apps without triggering vulernabilities.
@ndrezn
Copy link
Member

ndrezn commented Nov 27, 2024

We've had a few issues in the past with backwards incompatibilities in werkzeug causing issues in Dash (#1992) which led to the pin.

Could you open a ticket requesting that we release the upper bound for discussion? Want to make sure we get this right if we decide to change the dependency on werkzeug.

Add a `werkzeug` lower bound to ensure this vulnerability is not triggered: https://security.snyk.io/vuln/SNYK-PYTHON-WERKZEUG-8309092
@marcstern14
Copy link
Author

marcstern14 commented Nov 27, 2024

Yes will do! Thanks @ndrezn

edit: see issue here

@gvwilson gvwilson added P2 considered for next cycle fix fixes something broken dependencies Pull requests that update a dependency file labels Dec 3, 2024
@gvwilson
Copy link
Contributor

should be fixed in Dash 3.1.0 - thanks

@gvwilson gvwilson closed this Jun 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file fix fixes something broken P2 considered for next cycle

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants