rahulmansharamani14 opened a new pull request, #62279:
URL: https://github.com/apache/airflow/pull/62279

    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
      * closes: #61344
   
      Adds a dedicated `dag-versioning.rst` page under core concepts 
documenting AIP-65 (Dag versioning / improved Dag history in UI).
   
    **Changes:**                                                                
                                                                                
         
     - [x] New page `airflow-core/docs/core-concepts/dag-versioning.rst` 
covering:
       - How Dag versions are created and what they store                       
                                                                                
          
       - Four common scenarios with examples (Dag changes between runs, mid-run 
changes, task reruns across versions, clearing removed tasks)                   
          
       - UI reference (Graph view, Code tab, Details panels, Events tab)
       - Bundle version tracking (GitDagBundle vs LocalDagBundle)
       - Key behaviors summary table
     - [x] Screenshots for Scenario 1 (grid view) and Graph view (Dag Version 
dropdown)
     - [ ] Screenshots for Scenario 2 (Dag run details panel — mixed versions 
in a single run)
     - [ ] Screenshots for Scenario 3 (task instance details — version per try 
number)
     - [ ] Screenshots for Scenario 4 (disabled clear button on a removed task)
     - [x] Link to the new page from `core-concepts/dags.rst` and added to 
`core-concepts/index.rst` toctree
     - [x] Dag Versioning Q&A section added to `faq.rst`
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


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