The GitHub Actions job "Tests (AMD)" on 
airflow.git/feature/lang-sdk/taskflow-stub-dag has failed.
Run started by GitHub user jason810496 (triggered by jason810496).

Head commit for run:
7e2d0f229dd96fc98e997da99619652f36e2eabd / LIU ZHE YOU <[email protected]>
Ship arg_bindings in a new 2026-07-30 execution API version

The 2026-06-30 execution API version already shipped in Airflow 3.3.0, so
appending the arg_bindings migration to it would mutate a released version,
which the execution API versioning policy forbids; the change now opens
version 2026-07-30, matching the supervisor-schema date.

The rest addresses a local multi-reviewer audit of the branch:

- The airflow-go-pack integration test's expected manifest was missing the
  make_region task added to the example bundle, failing go test.
- The per-field cadwyn didnt_exist instructions on XComArgBinding and
  LiteralArgBinding name fields could never apply (arg_bindings is stripped
  wholesale on downgrade) and are dropped on both the execution API and the
  supervisor schema side; the supervisor-schema change class is renamed so
  the two same-named migrations cannot be confused.
- The stub decorator's hand-rolled version-split imports now go through the
  common.compat sdk seam (new PlainXComArg and KNOWN_CONTEXT_KEYS exports).
- The Go runtime validates required wire-spec fields (name, xcom task_id)
  instead of silently binding empty strings, populates the carried Kind
  discriminant, and reports a binding bookkeeping bug as a task error
  instead of panicking the worker.
- The supports_expand opt-out is now covered by task-sdk-level tests, the
  ti_run serialized-dag scan moved onto LazyDeserializedDAG next to its
  sibling accessors, and assorted review nits (exception types, stale
  wording, enum comparisons) are fixed.

Report URL: https://github.com/apache/airflow/actions/runs/29819249542

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to