Run CI on chart and airflow-ctl release-branch pull requests by potiuk · Pull Request #69626 · apache/airflow

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk · 2026-07-08T17:09:11Z

PRs targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all — those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm, and codeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 against chart/v1-2x-test).

This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same PR so the amd/arm guard keeps passing; push triggers get the -test variants only, matching the existing release-prep push convention.

Was generative AI tooling used to co-author this PR?

Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.

github-actions · 2026-07-08T17:40:20Z

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 6d155bb v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Pull requests targeting this branch received no CI at all: the airflow-ctl release-branch patterns were missing from the workflow trigger filters, so only branch-independent bot checks reported and a PR could show all-green without any tests or CodeQL ever running. GitHub resolves trigger filters from the workflow files on the target branch, so the equivalent fix on main (apache#69626) does not apply here and has to land on the release branch itself.

potiuk requested review from amoghrajesh, ashb, bugraoz93, gopidesupavan, jason810496 and jscheffl as code owners July 8, 2026 17:09

potiuk force-pushed the fix-ci-triggers-chart-airflowctl-branches branch from c704f36 to eb97efdCompare July 8, 2026 17:10

boring-cyborgBot added area:dev-tools backport-to-v3-3-test Backport to v3-3-test labels Jul 8, 2026

kaxil approved these changes Jul 8, 2026
View reviewed changes

gopidesupavan approved these changes Jul 8, 2026
View reviewed changes

potiuk merged commit 6d155bb into mainJul 8, 2026
145 of 156 checks passed

potiuk deleted the fix-ci-triggers-chart-airflowctl-branches branch July 8, 2026 17:38

potiuk mentioned this pull request Jul 8, 2026
[chart/v1-2x-test] Improve API server HTTPRoute configuration (#68552) #69579
Merged
1 task