Skip to content

Exclude suspended providers from selected-providers-list-as-string#62832

Merged
potiuk merged 3 commits intoapache:mainfrom
yuseok89:fix/provider-tests-exclude-suspended-providers
Mar 4, 2026
Merged

Exclude suspended providers from selected-providers-list-as-string#62832
potiuk merged 3 commits intoapache:mainfrom
yuseok89:fix/provider-tests-exclude-suspended-providers

Conversation

@yuseok89
Copy link
Contributor

@yuseok89 yuseok89 commented Mar 3, 2026

related: #61926

When provider files change, selective checks builds selected-providers-list-as-string and provider test types from affected providers and their dependencies.
Suspended providers (e.g. apache.beam) were included in these lists.

In #62791, provider test CI failed because apache.beam was included via Google provider dependencies.
This PR filters suspended providers from selected_providers_list_as_string and provider test types using get_suspended_provider_ids().


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)
    • Cursor

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Mar 3, 2026
@potiuk potiuk merged commit 82e5906 into apache:main Mar 4, 2026
250 checks passed
@github-actions
Copy link

github-actions bot commented Mar 4, 2026

Backport failed to create: v3-1-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-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 82e5906 v3-1-test

This should apply the commit to the v3-1-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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants