You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/05/05 18:35:30 UTC
[PR] Skip registry-derive in publish-docs for non-provider distributions [airflow]
potiuk opened a new pull request, #66438:
URL: https://github.com/apache/airflow/pull/66438
## Summary
The "Derive registry trigger inputs" step in
`publish-docs-to-s3.yml` runs
`python3 dev/registry/derive_wave_providers.py` unconditionally in
the Build Info job. The downstream `update-registry` job only runs
when `registry-providers != ''` or `registry-full-build == 'true'` —
so for non-provider distributions (`apache-airflow`,
`apache-airflow-ctl`, `apache-airflow-task-sdk`, `helm-chart`,
`docker-stack`) the script's output isn't consumed and the script
invocation is a no-op.
This PR skips the script invocation for those distributions:
- Both `registry-providers=` and `registry-full-build=false` are
set so the `update-registry` job skips downstream as expected.
- Release tags cut before #66100 (when the script was added) can
publish docs again without the workflow tripping on the missing
file. Surfaced while publishing docs for `airflow-ctl/0.1.4`
(cut from `0.1.4rc3` on 2026-04-22).
The non-provider list is kept in sync with `NON_PROVIDER_TOKENS` in
`dev/registry/derive_wave_providers.py`.
closes: #66436
## Test plan
- [x] `breeze workflow-run publish-docs --ref airflow-ctl/0.1.4 --workflow-branch airflow-ctl/0.1.4 apache-airflow-ctl` succeeded with the workflow YAML at the tag (workaround that exposed the issue): https://github.com/apache/airflow/actions/runs/25393124890
- [ ] After this PR lands: re-run publish-docs for airflow-ctl/0.1.4 against the workflow on `main` to verify the skip path works end-to-end with the new YAML.
- [ ] After this PR lands: re-run publish-docs for a wave-tag ref (e.g. `providers/2026-MM-DD`) to verify the provider path still invokes the script.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4.7)
Generated-by: Claude Code (Opus 4.7) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Skip registry-derive in publish-docs for non-provider distributions [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #66438:
URL: https://github.com/apache/airflow/pull/66438#issuecomment-4382586257
### Backport failed to create: v3-2-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/25399184530'> Run details </a>
Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
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](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel.
<table>
<tr>
<th>Status</th>
<th>Branch</th>
<th>Result</th>
</tr>
<tr>
<td>❌</td>
<td>v3-2-test</td>
<td><a href="https://github.com/apache/airflow/commit/73f273517aecba72b4141e82557fb669518cdeb2"><img src='https://img.shields.io/badge/Commit-73f2735-red' alt='Commit Link'></a></td>
</tr>
</table>
You can attempt to backport this manually by running:
```bash
cherry_picker 73f2735 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:
```bash
cherry_picker --continue
```
If you don't have cherry-picker installed, see the [installation guide](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-cherry-picker-cli).
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Skip registry-derive in publish-docs for non-provider distributions [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #66438:
URL: https://github.com/apache/airflow/pull/66438
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org