GitHub user potiuk added a comment to the discussion: DAG versioning behavior
Also to answer your question more preciseley: when you enable versioning in Airflow 3 bundle (which requires Bundle that supports it - for example GitBundle), what happens is that the version of Dag used when task is run is the same as the version available when dag-run got created. What happens when scheduler prepares new instances to run, it creates dag_runs in the table in a queued state. That DagRun has a reference to "version" of bundle that was in the database at the moment of creating the dag_runs. And those tasks from that DagRun when executed will checkout the version of the code that is linked with that bundle version (in case of GitBundle - they will check-out the commit that DagFileProcessor used last time when parsing that bundle. GitHub link: https://github.com/apache/airflow/discussions/59595#discussioncomment-15373880 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
