workflows: use task-sdk alias in publish-docs NON_PROVIDER_TOKENS#67279
Merged
Conversation
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>
eladkal
approved these changes
May 21, 2026
Contributor
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker f51d9e6 v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
publish-docs-to-s3.ymlfilters distributions through aNON_PROVIDER_TOKENSbash array, with a matching
frozensetindev/registry/derive_wave_providers.py.Both lists currently use the PyPI distribution name
apache-airflow-task-sdk,but
docs.build_docsitself accepts the docs-folder aliastask-sdk(see itsclickchoices). Invoking the workflow with either name fails:task-sdk: not inNON_PROVIDER_TOKENS, falls through todev/registry/derive_wave_providers.py— which does not exist on olderrelease branches like
v3-2-stable.apache-airflow-task-sdk: passes the filter butdocs.build_docsrejectsthe name with
Invalid value for '[apache-airflow | ... | task-sdk | ...]': 'apache-airflow-task-sdk' is not one of ....This PR replaces
apache-airflow-task-sdkwithtask-sdkin both lists sothe workflow can publish task-sdk docs end-to-end. The other references to
apache-airflow-task-sdkin the repo (pyproject templates, pip installcommands, PyPI URLs) are intentional PyPI distribution-name uses and are
left alone.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.7) following the guidelines