Skip to content

Add documentation for Dag versioning behavior#61605

Open
shleshaG wants to merge 2 commits intoapache:mainfrom
shleshaG:improve-dag-versioning-docs
Open

Add documentation for Dag versioning behavior#61605
shleshaG wants to merge 2 commits intoapache:mainfrom
shleshaG:improve-dag-versioning-docs

Conversation

@shleshaG
Copy link

@shleshaG shleshaG commented Feb 7, 2026

Adds documentation explaining DAG versioning behavior in Airflow 3,
clarifying how DAG runs are associated with DAG versions when
definitions change.

This improves clarity around DAG versioning for users reading
the core DAG concepts documentation.

related: #61344

Adds documentation explaining DAG versioning behavior in Airflow 3,
clarifying how DAG runs are associated with DAG versions when
definitions change.

Closes  apache#38571
@shahar1 shahar1 changed the title Add documentation for DAG versioning behavior Add documentation for Dag versioning behavior Feb 7, 2026
Copy link
Contributor

@shahar1 shahar1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, thanks for your contribution!
I fixed the linked issue in the description as it was wrong.
This wasn't my intention in the original issue - I would like to have a very detailed page with examples and screenshots, like the original AIP has.
I don't mind retaining the suggested changes after applying the terminology fix (DAG->Dag), but it won't close the issue from my prespective as we need a more detailed page.
Please note that someone else was assigned for completing the task as he had asked to be assigned first - so I'd kindly ask to let them finish it. Please feel free to work on other issues in the meanwhile.
If the current assignee becomes inactive after a week or two - you may ask to be assigned instead in the original issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants