go-sdk/pkg/execution/genmodels/models.gen.go is generated from the supervisor wire-schema
snapshot at task-sdk/src/airflow/sdk/execution_time/schema/schema.json, and it is behind it.
The snapshot last moved in #73224 and #73027; the models were last regenerated in #73531,
before both. Running just generate-models on current main adds two fields:
MultiTeam bool `msgpack:"multi_team,omitempty"`
RetryReason interface{} `msgpack:"retry_reason,omitempty"`
Nothing failed, because msgpack drops a field the struct does not declare — so the supervisor
sends these and the Go SDK cannot see them.
Nothing regenerates or verifies the file, which is why the drift went unnoticed across two PRs.
The Go SDK's Dag specs got a check for exactly this in #73936
(scripts/ci/prek/check_go_sdk_spec_drift.py): regenerate, then ask Git whether the committed
file changed.
To do
Drafted-by: Claude Code (Opus 5) (no human review before posting)
go-sdk/pkg/execution/genmodels/models.gen.gois generated from the supervisor wire-schemasnapshot at
task-sdk/src/airflow/sdk/execution_time/schema/schema.json, and it is behind it.The snapshot last moved in #73224 and #73027; the models were last regenerated in #73531,
before both. Running
just generate-modelson currentmainadds two fields:Nothing failed, because msgpack drops a field the struct does not declare — so the supervisor
sends these and the Go SDK cannot see them.
Nothing regenerates or verifies the file, which is why the drift went unnoticed across two PRs.
The Go SDK's Dag specs got a check for exactly this in #73936
(
scripts/ci/prek/check_go_sdk_spec_drift.py): regenerate, then ask Git whether the committedfile changed.
To do
models.gen.goand commit it.Drafted-by: Claude Code (Opus 5) (no human review before posting)