Skip to content

workflows: use task-sdk alias in publish-docs NON_PROVIDER_TOKENS#67279

Merged
vatsrahul1001 merged 1 commit into
mainfrom
fix-publish-docs-task-sdk-alias
May 21, 2026
Merged

workflows: use task-sdk alias in publish-docs NON_PROVIDER_TOKENS#67279
vatsrahul1001 merged 1 commit into
mainfrom
fix-publish-docs-task-sdk-alias

Conversation

@vatsrahul1001
Copy link
Copy Markdown
Contributor

@vatsrahul1001 vatsrahul1001 commented May 21, 2026

Summary

publish-docs-to-s3.yml filters distributions through a NON_PROVIDER_TOKENS
bash array, with a matching frozenset in dev/registry/derive_wave_providers.py.
Both lists currently use the PyPI distribution name apache-airflow-task-sdk,
but docs.build_docs itself accepts the docs-folder alias task-sdk (see its
click choices). Invoking the workflow with either name fails:

  • task-sdk: not in NON_PROVIDER_TOKENS, falls through to
    dev/registry/derive_wave_providers.py — which does not exist on older
    release branches like v3-2-stable.
  • apache-airflow-task-sdk: passes the filter but docs.build_docs rejects
    the name with Invalid value for '[apache-airflow | ... | task-sdk | ...]': 'apache-airflow-task-sdk' is not one of ....

This PR replaces apache-airflow-task-sdk with task-sdk in both lists so
the workflow can publish task-sdk docs end-to-end. The other references to
apache-airflow-task-sdk in the repo (pyproject templates, pip install
commands, PyPI URLs) are intentional PyPI distribution-name uses and are
left alone.

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 4.7)

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

The bash filter in publish-docs-to-s3.yml and the matching frozenset
in dev/registry/derive_wave_providers.py both listed
apache-airflow-task-sdk, but the inner docs.build_docs only accepts
the docs-folder alias task-sdk (see its click choices). Invoking the
workflow with either name fails:

- task-sdk: not in NON_PROVIDER_TOKENS, falls through to the registry
  script which does not exist on older release branches like v3-2-stable.
- apache-airflow-task-sdk: passes the filter but docs.build_docs
  rejects the name with "is not one of ... 'task-sdk', ...".

Replace apache-airflow-task-sdk with task-sdk in both lists so the
workflow can publish task-sdk docs end-to-end.

Discovered during the Airflow 3.2.2rc1 release.
Follow-up to #66438.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch

@vatsrahul1001 vatsrahul1001 merged commit f51d9e6 into main May 21, 2026
38 checks passed
@vatsrahul1001 vatsrahul1001 deleted the fix-publish-docs-task-sdk-alias branch May 21, 2026 10:05
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Airflow Registry May 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

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 Commit Link

You can attempt to backport this manually by running:

cherry_picker f51d9e6 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.

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

Labels

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

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants