Uh oh!
There was an error while loading. Please reload this page.
Fix scheduled CI upgrade failing when its PR already exists - #69018
Merged
Conversation
The scheduled "breeze ci upgrade" job force-pushes a stable branch (ci-upgrade-<branch>) and then looks for an existing PR before creating one. The lookup passed the "owner:branch" head label to "gh pr list --head", but that flag filters by the bare branch name only and does not support the "owner:branch" syntax, so the existing PR was never found and the job fell through to "gh pr create" — which rejected the duplicate and failed the run. Use the bare branch name for the "gh pr list" and "gh pr ready" lookups (only "gh pr create --head" needs the cross-fork "owner:branch" label), and treat an "already exists" creation error as success since the branch has already been force-pushed.
shahar1
requested review from
amoghrajesh, ashb, bugraoz93, choo121600, ephraimbuddy, gopidesupavan, jason810496, jedcunningham, jscheffl, potiuk and vatsrahul1001
as code ownersJune 26, 2026 08:02
potiuk
approved these changes
Jun 26, 2026
Uh oh!
There was an error while loading. Please reload this page.
Contributor
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actionsBot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Jun 26, 2026
…ts (apache#69018) The scheduled "breeze ci upgrade" job force-pushes a stable branch (ci-upgrade-<branch>) and then looks for an existing PR before creating one. The lookup passed the "owner:branch" head label to "gh pr list --head", but that flag filters by the bare branch name only and does not support the "owner:branch" syntax, so the existing PR was never found and the job fell through to "gh pr create" — which rejected the duplicate and failed the run. Use the bare branch name for the "gh pr list" and "gh pr ready" lookups (only "gh pr create --head" needs the cross-fork "owner:branch" label), and treat an "already exists" creation error as success since the branch has already been force-pushed. (cherry picked from commit 419ac06) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
potiuk pushed a commit
that referenced
this pull request
Jun 26, 2026
…ts (#69018) (#69055) The scheduled "breeze ci upgrade" job force-pushes a stable branch (ci-upgrade-<branch>) and then looks for an existing PR before creating one. The lookup passed the "owner:branch" head label to "gh pr list --head", but that flag filters by the bare branch name only and does not support the "owner:branch" syntax, so the existing PR was never found and the job fell through to "gh pr create" — which rejected the duplicate and failed the run. Use the bare branch name for the "gh pr list" and "gh pr ready" lookups (only "gh pr create --head" needs the cross-fork "owner:branch" label), and treat an "already exists" creation error as success since the branch has already been force-pushed. (cherry picked from commit 419ac06) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
karenbraganz pushed a commit
to karenbraganz/airflow
that referenced
this pull request
Jun 30, 2026
…9018) The scheduled "breeze ci upgrade" job force-pushes a stable branch (ci-upgrade-<branch>) and then looks for an existing PR before creating one. The lookup passed the "owner:branch" head label to "gh pr list --head", but that flag filters by the bare branch name only and does not support the "owner:branch" syntax, so the existing PR was never found and the job fell through to "gh pr create" — which rejected the duplicate and failed the run. Use the bare branch name for the "gh pr list" and "gh pr ready" lookups (only "gh pr create --head" needs the cross-fork "owner:branch" label), and treat an "already exists" creation error as success since the branch has already been force-pushed.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The scheduled
breeze ci upgradejob (.github/workflows/...→ "Scheduled CI upgrade check") force-pushes a stable branchci-upgrade-<branch>and then looks for an existing PR before creating one. The lookup passed theowner:branchhead label (e.g.apache:ci-upgrade-main) togh pr list --head, but that flag filters by the bare branch name only and explicitly does not support<owner>:<branch>syntax. So the existing PR was never found, the code fell through togh pr create, and GitHub rejected the duplicate — failing the run:(see run 28223885557)
Fix:
gh pr listandgh pr readylookups. Onlygh pr create --headneeds the cross-forkowner:branchlabel.already existscreation error as success (the branch has already been force-pushed, so the existing PR is up to date) — guards against a list/create race.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines