venkatamandavilli-code commented on issue #68612: URL: https://github.com/apache/airflow/issues/68612#issuecomment-4724861087
Thanks for the detailed report. This looks like an important issue because DAG versioning should ideally reflect meaningful DAG definition changes, not runtime-generated values that change on every run. The observation that setting `logical_date=None` stops the version from increasing is useful. It suggests that the default `logical_date` value in `TriggerDagRunOperator` may be introducing a dynamic timestamp into the serialized DAG representation, which then causes Airflow to treat each run as a new DAG version. From an operational perspective, this could create confusion in environments that rely on DAG version history for auditing, troubleshooting, and deployment traceability. If the DAG structure has not changed, the version should probably remain stable. It may be worth checking whether `logical_date` should be excluded from the serialized fields used for DAG version comparison, or whether the operator default should avoid evaluating a dynamic timestamp at parse/serialization time. -- 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]
