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

   # Why
   
   Release/backport branches (`v3-1-test`, `v3-2-test`, ...) often lack 
`go-sdk`/`java-sdk` entirely or
   carry a stale, branch-cut-frozen copy, so backporting a core/task-sdk fix to 
such a branch would
   silently run the lang-SDK coordinator k8s test against missing or outdated 
SDK sources.
   
   ## What
   
   - Added `_lang_sdk_fetch_upstream_sdk_sources()`: shallow-fetches upstream 
`main` (`upstream` remote if
     configured, else the canonical GitHub URL) and extracts 
`go-sdk`/`java-sdk` into a throwaway staging
     dir via `git archive`, never touching the real working tree.
   - Go build now runs against a scratch workspace mirroring `go_example`'s 
relative layout with `go-sdk`
     swapped for the upstream copy (its `go.mod` `replace` is a filesystem 
path, so this avoids editing
     it). Java build simply points gradle at the upstream `java-sdk` copy 
instead of the local one.
   - `airflow-core/`, `task-sdk/`, and the test's own harness fixtures 
(`go_example`/`java_example`) are
     untouched and keep tracking the checked-out branch. `providers/` is out of 
scope (unused by this test;
     overlaying it into the shared PROD image build isn't worth the 
invasiveness).
   - Lives entirely in breeze (`kubernetes_commands.py`), so it applies to both 
CI and local
     `breeze k8s setup-lang-sdk-test` — no CI workflow changes needed.
   
   Known tradeoff: this makes the lang-SDK test provisioning require network 
access to GitHub, which it
   didn't before.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes, with help of Claude Code Sonnet 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: [email protected]

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

Reply via email to