dstandish commented on PR #31987: URL: https://github.com/apache/airflow/pull/31987#issuecomment-1672117025
> @dstandish We also need to think about triggers in the different providers and how to make them b/c; should we add an ugly Airflow version check in each trigger to know if we should yield an event or return it, or we only change the core triggers (`airflow/triggers/*`) and wait until bumping the minimum version of Airflow in providers to 2.7.x to make the change Yes, valid concern, future compat is something we must deal with pretty regularly though, nothing terribly unusal here. I.e. it's common that we add some new interface or feature in core and we have to wait for min airflow version of provider to catch up before using it. Related note, I actually have a PR on the shelf to add some amount of automation / alerting to help us with this kind of thing... i.e. reminding us to remove deprecations, or to remove future compat checks, or to update code at X min-airflow-version. I had to drop it to focus on AIP-52 but hope to pick it up again soon. -- 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]
