Introduce lower bind to lxml as 5.4.0 #49612
Merged
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
Contributor
Author
|
I do not know if this is the best fix, but something i wanted to try |
Contributor
Author
|
Reopening to run all tests |
potiuk
approved these changes
Apr 23, 2025
prabhusneha
pushed a commit
to astronomer/airflow
that referenced
this pull request
Apr 25, 2025
31 tasks
potiuk
pushed a commit
to potiuk/airflow
that referenced
this pull request
May 5, 2025
(cherry picked from commit 9eb5c33) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
potiuk
added a commit
that referenced
this pull request
May 5, 2025
31 tasks
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.
Recent failure in CI: https://github.com/apache/airflow/actions/runs/14613850677/job/40997825403 is due to:
lxml released a 5.4.0 which doesnt seem to work with 1.3.14 xmlsec. And this is not resolved: xmlsec/python-xmlsec#344 so we cannot even remove the !=1.3.15 on xmlsec.
Hence, trying to fix by adding bounds to
lxmlinstead^ 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 airflow-core/newsfragments.