+1 (binding), checked: - Checksums - Signature - Source matches tag - No binaries - Licence - Build from source - Go module proxy zip matches tag
Best regards, Wei Lee On Wednesday, November 11th, 2026 at 3:18 PM, Amogh Desai via dev <[email protected]> wrote: > +1 binding. > > Validated: > - SHA-512 checksum matches (shasum -a 512 -c) > - GPG signature is good, key is in KEYS > - Source tarball matches go-sdk/ at the tag (a264c38) > - No binary files in the source package > - LICENSE and NOTICE present > - go vet passes & just build packs the example bundles > - Cross-builds for linux/386 and linux/arm pass (the 32-bit fix) > - go get github.com/apache/airflow/[email protected] resolves from the > proxy, checksum database agrees, proxy origin is the same tag/commit > > Two small issues I noticed (non blocking) > > 1. *TestRuleConstantsMatchPython* fails when run from the source release. > It reads *airflow-core/src/airflow/task/{trigger,weight}_rule.py* from > the monorepo, which is not in the tarball. DEVELOPMENT.md says a > standalone source release can test without the monorepo, so this test > should skip when those files are absent, or vendor them like the > schemas. All tests pass from a tag checkout, though > 2. *TestTriggerDagRunRejectsAnInvalidSpec* fails on Go 1.27 because it matches > encoding/json exact error text, which changed. It passes on > golang 1.25 (the CI version). The validation itself works, and only the > expected string is version specific. > > Thanks & Regards, > Amogh Desai > > > On Tue, Nov 10, 2026 at 1:44 PM Zhe-You(Jason) Liu via dev < > [email protected]> wrote: > > > +1 (non-binding) > > > > Checked: > > - Source package: checksum and signature OK, contents identical to the > > go-sdk/v1.0.0-rc1 tag, LICENSE and NOTICE present, no binaries. > > - go mod verify, build, vet and tests pass with Go 1.25.13 (the CI > > version). > > - The module on proxy.golang.org is identical to the source package. > > - Vendored schemas match Airflow 3.4.0. > > > > Thanks, > > Jason > > > > On Tue, Nov 10, 2026 at 3:56 PM Tzu-ping Chung via dev < > > [email protected]> wrote: > > > > > Hi, > > > > > > I would like to call a vote to release Apache Airflow Go SDK 1.0.0, based > > > on release candidate 1.0.0-rc1. > > > > > > Changes since 1.0.0-beta4: fixes the Go SDK build on 32-bit targets, the > > > install command breaking the first bundle build, and log attributes > > > displacing standard log fields; ti_run now loads the serialized Dag only > > > for stub tasks. > > > > > > The release candidate contains the Go module > > > github.com/apache/airflow/go-sdk. > > > > > > Git information: > > > > > > - Tag: go-sdk/v1.0.0-rc1 > > > - Commit: a264c38fdd66c0239e01357ddd72e9631a4bcbb7 > > > - https://github.com/apache/airflow/releases/tag/go-sdk%2Fv1.0.0-rc1 > > > > > > Source release, signatures and checksums: > > > https://dist.apache.org/repos/dist/dev/airflow/go-sdk/1.0.0-rc1/ > > > > > > To try the release candidate in a Go project: > > > > > > go get github.com/apache/airflow/[email protected] > > > > > > KEYS file (public keys used to sign the release): > > > https://downloads.apache.org/airflow/KEYS > > > > > > Please review and vote. The vote will remain open for at least 72 hours, > > > until 2026-11-14 08:00 UTC, or until the necessary number of binding > > votes > > > is reached. > > > > > > [ ] +1 Release this package as Apache Airflow Go SDK 1.0.0 > > > [ ] +0 No opinion > > > [ ] -1 Do not release, because ... > > > > > > Only votes from Airflow PMC members are binding, but everyone is welcome > > > and encouraged to test the release and vote. > > > > > > The verification process can be found in the main repository. This > > > currently reused Java SDK's verification guide; the section will be moved > > > to a better location later. > > > > > > > > https://github.com/apache/airflow/blob/main/java-sdk/DEVELOPMENT.md#verifying-a-release > > > > > > For more details on ASF release verification, see: > > > https://www.apache.org/info/verification.html > > > > > > Best, > > > TP > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
