Remove werkzeug upperbound #3095
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`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.
marcstern14
requested review from
alexcjohnson,
T4rk1n,
ndrezn,
gvwilson and
emilykl
as code owners
|
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
gvwilson
added
P2
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
werkzeug>=3.1is compatible within the set flask boundaries. Removing the boundaries forwerkzeugwould allow for more flexible installations on deployed apps without triggering vulnerabilities.