[PR] Fix Publish Docs to S3 failing for ts-sdk and java-sdk [airflow]

["jason810496 (via GitHub)" <gi...@apache.org>]

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

   - related: #70812, #66100
   - failing run: https://github.com/apache/airflow/actions/runs/32948512400
   
   ## Why
   
   Dispatching **Publish Docs to S3** with `include-docs=ts-sdk` fails: `ts-sdk` is passed to the registry as a provider ID, extraction exits 1 with `provider(s) not found in provider.yaml files: ['ts-sdk']`, and that blocks the publish. `java-sdk` has the same latent bug.
   
   ## How
   
   The non-provider token list is hand-copied in three places, and two were missing both SDK tokens:
   
   - `.github/workflows/publish-docs-to-s3.yml` (bash array), stale
   - `dev/registry/derive_wave_providers.py` (`NON_PROVIDER_TOKENS`), stale
   - `dev/breeze/src/airflow_breeze/utils/publish_docs_to_s3.py` (`NON_SHORT_NAME_PACKAGES`), in sync but unpinned
   
   The duplication is deliberate (the bash copy lets release tags predating #66100 still publish), so rather than removing it, tests pin all three to breeze's `REGULAR_DOC_PACKAGES`:
   
   ```
   NON_PROVIDER_TOKENS == set(REGULAR_DOC_PACKAGES) - META_TOKENS
   ```
   
   Anchoring to `REGULAR_DOC_PACKAGES` is the point: #70812 added `ts-sdk` there and to the workflow but never touched `dev/registry/`, so only this direction catches that drift. `registry-tests.yml` also only triggered on `dev/registry/**`, so such a PR ran no check at all.
   
   ## What
   
   - Add `java-sdk` and `ts-sdk` to both stale copies.
   - Add three drift guards in `dev/registry/tests/test_derive_wave_providers.py`, one per copy. They raise rather than silently pass if their pattern stops matching, and the AST helper rejects non-literal elements, which would otherwise shrink both sides of the comparison in step and pass vacuously.
   - Add `test_derive` cases `ts-sdk`, `java-sdk ts-sdk task-sdk`, and `ts-sdk amazon` (a real provider alongside an SDK token must still rebuild).
   - Widen `registry-tests.yml` `pull_request` paths to cover `publish-docs-to-s3.yml` and `global_constants.py`.
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes, with help of Claude Code Opus 5 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] Fix Publish Docs to S3 failing for ts-sdk and java-sdk [airflow]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on PR #72097:
URL: https://github.com/apache/airflow/pull/72097#issuecomment-5424446156

   ### Backport failed to create: v3-3-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/32961911931'> 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-3-test</td>
           <td><a href="https://github.com/apache/airflow/commit/d31c984dc67a0cd60b111c3d903b1d5e4ced0c93"><img src='https://img.shields.io/badge/Commit-d31c984-red' alt='Commit Link'></a></td>
       </tr>
   </table>
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker d31c984 v3-3-test
   ```
   
   This should apply the commit to the v3-3-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.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] Fix Publish Docs to S3 failing for ts-sdk and java-sdk [airflow]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk merged PR #72097:
URL: https://github.com/apache/airflow/pull/72097


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