Repository navigation
Remove v3-2-test scheduled CI upgrade check - #68275
Merged
Lee-W merged 1 commit intoJun 9, 2026
Merged
Conversation
No further 3.2.x releases are planned, so the scheduled CI upgrade check for the v3-2-test branch is no longer needed. - Delete the scheduled-upgrade-check-v3-2-test.yml caller workflow - Drop the stale v3-2-test example from the reusable upgrade-check workflow input description
Lee-W
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
June 9, 2026 07:45
potiuk
approved these changes
Jun 9, 2026
1 task done
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
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.
Why
No further 3.2.x releases are planned, so the scheduled CI upgrade check for the v3-2-test branch is no longer needed.
What
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.