Fix DagVersion when clearing tasks with run on latest version#65835
Merged
bbovenzi merged 7 commits intoMay 1, 2026
Conversation
yuseok89
force-pushed
the
fix/clear-run-on-latest-dag-version
branch
from
4b01db9 to
0144302
Compare
yuseok89
requested review from
XD-DENG,
ashb,
bbovenzi,
choo121600,
guan404ming,
pierrejeambrun,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
potiuk
added
the
ready for maintainer review
bbovenzi
added
the
backport-to-v3-2-test
bbovenzi
reviewed
Apr 27, 2026
Contributor
bbovenzi
left a comment
bbovenzi
left a comment
There was a problem hiding this comment.
Looking good. A few UI nits.
…test-dag-version # Conflicts: # airflow-core/src/airflow/ui/src/components/Clear/TaskInstance/ClearTaskInstanceDialog.tsx
Contributor
Author
|
@bbovenzi |
bbovenzi
approved these changes
Apr 29, 2026
Contributor
|
LGTM except for static check issues |
bbovenzi
reviewed
Apr 29, 2026
yuseok89
force-pushed
the
fix/clear-run-on-latest-dag-version
branch
from
cbe5d33 to
ed47bed
Compare
Contributor
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 8c43743 v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
1 task
bbovenzi
pushed a commit
that referenced
this pull request
May 14, 2026
#66901) * Fix DagVersion when clearing tasks with run on latest version * UI: Merge two useEffects in ClearGroupTaskInstanceDialog * UI: Add spacing between clear task checkboxes * UI: Share run on latest version logic for clear dialogs * UI: Merge two useEffects in ClearTaskInstanceDialog * Fix CI: apply pre-commit auto-fixes (cherry picked from commit 8c43743) Co-authored-by: Yuseok Jo <yuseok89@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Problem
After clearing one task with "run on latest version", clearing another task in the same DagRun showed that task was not on the latest DagVersion. In the same situation, the "run with latest version" checkbox did not appear. The checkbox was gated on
bundle_versionchanges, so it stayed hidden when only DagVersion numbers differed.Solution
latest_dag_version.version_number≠ the clear target’s versiondag_version_idonly on cleared task instances, while still pointing the DagRun at the latestBefore
Screen.Recording.2026-04-25.at.12.07.41.AM.mov
After
Screen.Recording.2026-04-25.at.11.57.04.PM.mov
Screen.Recording.2026-04-25.at.11.58.04.PM.mov
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.