jscheffl commented on PR #64143: URL: https://github.com/apache/airflow/pull/64143#issuecomment-4147766982
> Wait, I realized that we still need those fallback to keep it compatible or we might cause breaking change for users who using older Airflow in the last minute. > > Let me explain why: users could still use latest providers in "older" Airflow Core (e.g. Airflow `3.1` or `2.11`), for the `conf` in older Airflow version, they don't respect the `provider.yaml`. That is the reason why we have the "common.compat" provider - to abstract the Airflow backend version away. So as the change is made and depednency in modelled in provider.yaml this should be fine. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
