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/08/14 20:04:23 UTC

[PR] Fix lang-SDK k8s test on release branches by using their own SDKs [airflow]

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

   The lang-SDK k8s test fetched `go-sdk/`/`java-sdk/` from upstream `main` on any
   run not targeting `main`, on the assumption that a release branch either lacks
   them or carries a stale copy.
   
   That copy isn't stale — it's the matching one. A packed bundle declares a dated
   `supervisor_schema_version` and the task-SDK supervisor refuses a bundle whose
   version it doesn't know, so upstream `main`'s SDK cannot run against a release
   branch's Airflow at all. `_lang_sdk_resolve_sdk_sources()` now builds from the
   checkout's own `go-sdk`/`java-sdk` whenever it has them; the upstream-`main`
   fetch stays only as the fallback for a branch cut before those directories
   existed. No behaviour change for `main`, which always has them.
   
   Seen on `v3-3-test`, where every run of `K8S Lang-SDK` has failed since `main`
   moved to supervisor schema `2026-10-30` while the branch is on `2026-06-16`:
   `go_extract` dies with `cannot find executable bundle with usable
   supervisor_schema_version`.
   
   related: #71527
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: 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 lang-SDK k8s test on release branches by using their own SDKs [airflow]

Posted by "jason810496 (via GitHub)" <gi...@apache.org>.
jason810496 merged PR #71639:
URL: https://github.com/apache/airflow/pull/71639


-- 
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 lang-SDK k8s test on release branches by using their own SDKs [airflow]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #71639:
URL: https://github.com/apache/airflow/pull/71639#issuecomment-5300374884

   ### Backport failed to create: v3-3-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/31862593697'> 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/39d801aa89d9ce7a8a38487a377cb3f6d076efee"><img src='https://img.shields.io/badge/Commit-39d801a-red' alt='Commit Link'></a></td>
       </tr>
   </table>
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 39d801a 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