-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Remove AIRFLOW_2_10_PLUS conditions #49877
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
Conversation
eladkal
left a comment
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.
Nice!
I just started to work on it too :)
Missing handling of test_when_provider_min_airflow_version_is_2_10_or_higher_remove_obsolete_code in azure provider
7ee022d to
12a26be
Compare
I will leave that one to @dabla :) |
9a5b958 to
b8e09c8
Compare
fb9acfd to
298661c
Compare
jscheffl
left a comment
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.
Nice cleanup!
After updating providers to 2.10+ we can remove all conditions for 2.10+.
298661c to
de0b7df
Compare
After updating providers to 2.10+ we can remove all conditions for 2.10+.
After updating providers to 2.10+ we can remove all conditions for 2.10+.
After updating providers to 2.10+ we can remove all conditions for 2.10+.
After updating providers to 2.10+ we can remove all conditions for 2.10+.
^ 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.