choo121600 opened a new pull request, #53216:
URL: https://github.com/apache/airflow/pull/53216
## Summary
Adds visual indicators in the Grid view to help users identify DAG version
changes and detect mixed-version TaskInstances within a single DagRun.
## Problem
* After updating a DAG file, it's difficult to know from which DagRun the
new version is applied.
* Some TaskInstances within the same DagRun may use different DAG versions,
but this is not visible in the UI.
## Solution
This PR introduces visual cues in the Grid view to address these pain points:
* Version Change Indicator(Vertical):
* A vertical orange line on the left of a DagRun indicates a DAG version
change.
* The label shows the new version number (e.g., v2).
* Mixed Version Indicator(Vertical):
* A vertical orange line on the right of a DagRun denotes that multiple
DAG versions were used in its TaskInstances.
* TaskInstance Version Dividers(Horizontal):
* Horizontal orange lines separate TaskInstances using different DAG
versions within the same DagRun.
<img width="2168" height="1397" alt="image"
src="https://github.com/user-attachments/assets/55157a58-731e-486a-84e4-e56e7ec203be";
/>
<img width="828" height="907" alt="image"
src="https://github.com/user-attachments/assets/e2b379c0-0ae7-4a05-9c87-3ab102597eff";
/>
## Change
### Backend
Introduced a new DagVersionService that:
* Efficiently detects version changes and mixed-version runs using a single
optimized query.
* Returns version metadata to the UI through the /grid/runs/{dag_id} API.
Extended API response models to include:
* dag_version_id, dag_version_number, latest_version_number
* is_version_changed, has_mixed_versions
### Frontend
* Added `VersionIndicator` component in `Grid bars` to display version
change and mixed-version status.
* Integrated version dividers between TaskInstances in
`TaskInstancesColumn.tsx`.
* Ensured accessibility with aria-label for screen reader support.
* Used orange theme (orange.400 for background, orange.700 for version text).
closes: #52286
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! 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 committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a
newsfragment file, named `{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]
