Fix publish-docs Update Provider Registry job for non-provider distributions

[potiuk]

Triggering the Publish Docs to S3 workflow with apache-airflow-ctl (or apache-airflow-task-sdk) has the docs publishing succeed but the downstream Update Provider Registry / Build & Publish Registry job fail with:

ERROR: provider 'apache-airflow-ctl' not found in provider.yaml files

Observed on run https://github.com/apache/airflow/actions/runs/24630652716 while publishing docs for airflow-ctl/0.1.4rc2.

Cause

publish-docs-to-s3.yml computes the registry-update list in the build-info job. The case statement that filters out non-provider packages (apache-airflow, all-providers, apache-airflow-providers, helm-chart, docker-stack) did not include apache-airflow-ctl or apache-airflow-task-sdk, so those names fell through to the default branch and were added to REGISTRY_PROVIDERS. The downstream registry-build.yml workflow then called dev/registry/extract_parameters.py --provider apache-airflow-ctl, which exits 1 because airflow-ctl is not a provider.

Fix

Extend the skip list to include apache-airflow-ctl and apache-airflow-task-sdk so the registry-update job is correctly skipped for these distributions (matching the existing behaviour for apache-airflow and helm-chart).

Docs publishing itself is unaffected — this change only stops surfacing a red check on every airflow-ctl / task-sdk docs publish.

---

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

• Yes — Claude Opus 4.7 (1M context)

Generated-by: Claude Opus 4.7 (1M context) following the guidelines

[github-actions]

Backport failed to create: v3-2-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-2-test

You can attempt to backport this manually by running:

cherry_picker 6beb521 v3-2-test

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