Update logic and fix false-positive of dag version inflation checker #61345
+163
−29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
related: https://apache-airflow.slack.com/archives/C06K9Q5G2UA/p1769642556328069?thread_ts=1769631389.812549&cid=C06K9Q5G2UA
Improve: #59430
I improve the logic by checking various cases and identifying undetected or incorrectly detected scenarios from the initial version.
sdk.DAG(dag_id='dag_id')was not detected when used instead ofDAG(dag_id='dag_id').@taskthat are serialized by plain code.with DAGblocks, but now modified to only check functions whose names end withOperatororTask.Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.