The GitHub Actions job "Tests" on airflow.git/fix-deactivate-legacy-dags-null-bundle has succeeded. Run started by GitHub user kalluripradeep (triggered by kalluripradeep).
Head commit for run: ee0fb5f019e7c5e0714422b98e351140a5f95949 / kalluripradeep <[email protected]> Fix #60763: Deactivate legacy DAGs with NULL bundle_name during upgrade from 2.x to 3.x When upgrading from Airflow 2.x to 3.0.6, DAGs that are removed during the upgrade are not deactivated because they have bundle_name=NULL. The deactivation logic in deactivate_stale_dags() only queries DAGs where bundle_name is in the current bundle_names set, completely excluding legacy DAGs with NULL bundle_name. This fix modifies the query to also include DAGs with NULL bundle_name, ensuring that removed legacy DAGs are properly deactivated during upgrades from 2.x to 3.0.x. Note: In Airflow 3.1.0+, migration 0082 sets NULL bundle_names to 'dags-folder' by default, but users on 3.0.x still have NULL values. Report URL: https://github.com/apache/airflow/actions/runs/21321498968 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
