vatsrahul1001 opened a new issue, #49606: URL: https://github.com/apache/airflow/issues/49606
### 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 - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
