Bring back providers compatibility checks #52398
Conversation
445f766 to
44e6bf9
Compare
44e6bf9 to
b6a0ed5
Compare
|
I don't think we need to backport to 3.0? |
|
Yeah. No need. Removed it ... I also have hard time figuring out how the compatibility of the links /test should be fixed. Anyone can help with it and provide fixup :) ? Especially if you know more about the context/ti changes between Airflow 2 and 3? |
Yeah looking it now. |
b6a0ed5 to
3cc82b4
Compare
OK. I have a fix. |
The compatibility checks were removed in apache#52072 accidentally. This one brings them back: * Python 3.10 * do not add cloudant (it was not working for Python 3.9)
3cc82b4 to
bb4e943
Compare
The compatibility checks were removed in #52072 accidentally. This one brings them back:
^ 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.