Use different default algorithms for different werkzeug versions #46384
Conversation
This file contains hidden or 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
Older werkzeug uses different algorithms for different versions - we should match the default algorithm for those versions.
potiuk
force-pushed
the
set-default-algorithm-for-hashing-based-on-werkzeug-version
branch
from
6f97492 to
74be557
Compare
vincbeck
reviewed
Feb 3, 2025
providers/fab/src/airflow/providers/fab/auth_manager/security_manager/override.py
Show resolved
Hide resolved
vincbeck
approved these changes
Feb 3, 2025
potiuk
deleted the
set-default-algorithm-for-hashing-based-on-werkzeug-version
branch
Backport successfully created: providers-fab/v1-5
|
github-actions bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Feb 3, 2025
…erkzeug versions (apache#46384) Older werkzeug uses different algorithms for different versions - we should match the default algorithm for those versions. (cherry picked from commit dafd166) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
Feb 4, 2025
…erkzeug versions (#46384) (#46392) * [providers-fab/v1-5] Use different default algorithms for different werkzeug versions (#46384) Older werkzeug uses different algorithms for different versions - we should match the default algorithm for those versions. (cherry picked from commit dafd166) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> * Add evaluation extra to google-cloud-aiplatform (#46270) The scikit-learn is an optional dependency of the library from google and apparently we are using the `evaluation` optional feature of it. Adding the extra should make google provider depends on scikit-learn. Closes: #46258 Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com> (cherry picked from commit baf54a8) --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
niklasr22
pushed a commit
to niklasr22/airflow
that referenced
this pull request
Feb 8, 2025
…che#46384) Older werkzeug uses different algorithms for different versions - we should match the default algorithm for those versions.
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 17, 2025
…che#46384) Older werkzeug uses different algorithms for different versions - we should match the default algorithm for those versions.
This was referenced Apr 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Older werkzeug uses different algorithms for different versions - we should match the default algorithm for those versions.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.