leeyspaul commented on issue #65793: URL: https://github.com/apache/airflow/issues/65793#issuecomment-4381668748
@potiuk @shahar1 OK, so I'm continuing focus on CeleryExecutor. Given the minimum version announcement: https://github.com/apache/airflow/blob/main/providers/PROVIDER_RELEASES.rst Suggested scope for Celery path: - current Celery provider source against Airflow 3.1.x - current Celery provider source against Airflow main/current dev - Nice-to-have: Airflow 3.0.x as a lower-bound Airflow 3 sanity check while provider minimum support is transitioning Out of scope: - exhaustive Airflow 2.x coverage, since Airflow 2 reached EOL on April 22, 2026, and provider policy says the minimum provider Airflow version is expected to move to Airflow 3.1.0 after May 20, 2026. The main goal would be catching import-time and workload execution compatibility regressions in CeleryExecutor / `celery_executor_utils`, especially around version-gated symbols and behavior such as `ExecutorWorkload`, `BaseExecutor.run_workload`, `ExecuteCallback`, `ExecutorConf`, and `external_executor_id`. If that sounds right, I can open a CeleryExecutor-specific sub-issue under this meta issue (unsure if I have the permissions for that). -- 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]
