Bundle version in dag_version table not updated when DAG code changes do not trigger a new dag_version

[vatsrahul1001]

Apache Airflow version

3.0.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

The bundle_version field in the dag_version table is not updated when DAG code changes do not trigger a new dag_version.

For example, making a minor code change like adding a print statement does not create a new dag_version, but it does create a new bundle_version in the dag_bundle table. However, this updated bundle_version is not reflected in the dag_version table.

As a result, the UI continues to show the older bundle_version, even though the new DAG code is picked up during execution

What you think should happen instead?

The bundle_version field in the dag_version table should be updated regardless of whether a new dag_version is created, to reflect the most recent DAG code and avoid misleading information in the UI.

How to reproduce

1. Create a git dag bundle.
2. Update a print statement in dag
3. Verify In UI or dag_version table still old bundle version is reflecting

Operating System

Linux

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dstandish]

What you think should happen instead?
The bundle_version field in the dag_version table should be updated regardless of whether a new dag_version is created, to reflect the most recent DAG code and avoid misleading information in the UI.

Or perhaps we should create a new dagversion record if EITHER dag code changes OR bundle version changes.

[Felix-neko]

Or perhaps we should create a new dagversion record if EITHER dag code changes OR bundle version changes.

I think that this behaviour could be configurable: airflow could delete the DAG from previous bundle version and create a new DAG by default -- and keep it and just create another version if corresponding field in airflow.cfg is enabled.

But if it's hard to implement -- just for now airflow could just delete previous DAG every time if there is not DAG with such name in new bundle version.

P.S. We also need this fix, it's really useful.