venkatamandavilli-code commented on issue #59319:
URL: https://github.com/apache/airflow/issues/59319#issuecomment-4724939371

   Thanks for the detailed investigation and reproduction steps.
   
   The observation that the behavior disappears when `logical_date=None` is 
specified seems like a very useful clue.
   
   From a DAG versioning perspective, I would expect versions to change when 
the DAG definition changes, not when a DAG is executed. If a runtime-generated 
timestamp is being included in the serialized representation used for version 
comparison, that could explain why a new version is created for every run.
   
   The fact that removing the `TriggerDagRunOperator` also resolves the issue 
seems to further suggest that the operator's default `logical_date` handling 
may be contributing dynamic content during serialization.
   
   This could have operational implications because frequent version changes 
may make it harder to use DAG versions for auditing, deployment validation, and 
troubleshooting.
   
   It may be worth checking whether the default `logical_date` value is 
evaluated during DAG parsing/serialization and whether it should be excluded 
from fields that participate in DAG version calculation.
   


-- 
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]

Reply via email to