jason810496 opened a new issue, #66938: URL: https://github.com/apache/airflow/issues/66938
### Background Three artefacts ship together for the Go-SDK / executable-coordinator story but have no agreed release process today: 1. The Go module under `go-sdk/` (consumed via `go install [email protected]`). 2. The `airflow-go-pack` build tool (`go-sdk/cmd/airflow-go-pack/`), used at *bundle build time* to append the `AFBNDL01` trailer (ADR 0004). 3. The Python provider distribution `apache-airflow-providers-sdk-executable` (`providers/sdk/executable/`), which the Airflow task runner loads. The Java-SDK side has the same problem and is tracking it under #66333. ### What needs to happen 1. Decide the cadence and version-skew matrix between the three artefacts (e.g. does `airflow-go-pack vX` produce bundles that any `providers-sdk-executable vY` can consume?). 2. Add release tooling: tagging convention, changelog generation, `pyproject.toml` version bumping for the provider, Go module tagging for the SDK and packer. 3. Document how a Go-SDK user installs the matched set. ### Acceptance criteria - Documented release procedure for each of the three artefacts. - Version-compatibility matrix is captured (probably in `providers/sdk/executable/docs/`). - A first 0.1 release can be cut following the documented procedure. ### Context - Java parallel: #66333 (Release Management for Java-SDK). - Bundle-spec format version is currently `1.0` (see `providers/sdk/executable/docs/bundle-spec.rst`); we should align release versioning with this. --- Drafted-by: Claude Code (Opus 4.7) (no human review before posting) -- 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]
