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

   "Build Java SDK Javadoc" and "Build TypeScript SDK API reference" took a 
runner on every docs publish, only for a step inside each job to decide there 
was nothing to build. That is the usual case: providers waves, core, airflowctl 
and Helm chart publishes do not ask for the SDK docs, and an `all` build of an 
older ref may have no SDK, or only a `-SNAPSHOT` Java version.
   
   The decision now runs in `build-info`, which already checks out the ref. It 
is the same logic, moved unchanged. The two SDK jobs are skipped with a 
job-level `if:` when there is nothing to build. They check out the commit 
`build-info` decided on (`sdk-docs-sha`), so a moving branch or a re-run of a 
failed SDK job cannot build a commit the decision did not see, such as a 
`-SNAPSHOT` version. `publish-docs-to-s3` accepts a skipped SDK job. It still 
requires `build-docs` to succeed, and that job needs the same `build-info` and 
`runner-info`, so a skip caused by a failed dependency still blocks publishing.
   
   Checks run:
   - prek hooks on the workflow, including zizmor and yamllint, pass.
   - actionlint reports only the existing `fromJSON` error at the actor 
allowlist (line 152), which is also on `main`.
   - Two independent adversarial reviews (Copilot CLI, gpt-6.1-sol). Round 1 
found the decision/build commit race described above; it is fixed by the SHA 
pin. Round 2 gave GO from both.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5.5)
   
   Generated-by: Claude Code (Opus 5.5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


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