vatsrahul1001 opened a new pull request, #67279:
URL: https://github.com/apache/airflow/pull/67279

   ## 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.
   
   ## Repro
   
   Discovered during the Airflow 3.2.2rc1 release. Run
   https://github.com/apache/airflow/actions/runs/26216945618 fails at the
   `Build documentation` step:
   
   ```
   Invalid value for '...': 'apache-airflow-task-sdk' is not one of
   'apache-airflow', ..., 'task-sdk', ..., 'docker-stack'.
   ```
   
   ## Related
   
   Follow-up to #66438 which introduced `NON_PROVIDER_TOKENS`.
   
   ## Test plan
   
   - [ ] After merge, re-run `breeze workflow-run publish-docs --ref 3.2.2rc1 
--site-env staging apache-airflow docker-stack task-sdk` and confirm both the 
filter step and `Build documentation` step pass.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to