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

   Airflow 3 stores one `serialized_dag` row per Dag version, but `airflow dags 
list`
   selected every row without filtering by version, so a Dag was printed once 
per
   version it had.
   
   Use the existing `SerializedDagModel.read_all_dags()` helper, which selects 
the
   row with the highest `version_number` per `dag_id`.
   
   Note that #60868 / #61077 fixed one source of *spurious* version growth, but
   legitimate versions still accumulate whenever a Dag is edited, so the 
duplicate
   rows remain reproducible.
   
   closes: #60594
   
   This supersedes #60637, which reached the same diagnosis but was closed by 
the
   stale bot without review.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: Claude Code (Opus 5) 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`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


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