jason810496 opened a new pull request, #67153:
URL: https://github.com/apache/airflow/pull/67153
## Why
Capture the design decisions behind the next slice of Go SDK work — how
bundles are packed, which packer mechanism we adopt, how the bundle
binary speaks the coordinator protocol, and how the artefact is
shipped. These ADRs are the contract the follow-up implementation PRs
build against, so they need to land first (and stand on their own as
documentation).
## What
- ADR 0001: register the post-build bundle-packing options for the Go
SDK and pick the option set we'll deliver (standalone packer + Go
1.24 `tool` directive + standardised `--dump-bundle-spec`).
- ADR 0002: select the Go 1.24 `tool` directive as the delivery
mechanism for the bundle packer; rationale for not vendoring a CLI
or shipping a separate distribution.
- ADR 0003: define the dual-mode bundle binary — a coordinator-protocol
msgpack-over-IPC path alongside the existing go-plugin/Edge-Worker
path — so the same binary can run under both task execution models.
- ADR 0004: switch the bundle artefact to a self-contained executable
with footer-embedded source and metadata; supersedes the ZIP-archive
shape from ADRs 0001/0002 while keeping the same packer mechanism.
---
##### Was generative AI tooling used to co-author this PR?
- [x] Yes, with help of Claude Code Opus 4.7 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]
