zeroshade opened a new pull request, #857: URL: https://github.com/apache/arrow-go/pull/857
### Rationale for this change The RC `Verify` job does not pin Go via `actions/setup-go`. `dev/release/verify_rc.sh`'s `ensure_go()` reuses whatever Go is already on the runner and only downloads the latest Go when none is present — it never checks the installed version against the module's required `go` directive. On runners whose preinstalled Go is older than the module's `go` directive (currently `go 1.25.0`), the verify build resolves to that older Go's language version and fails to compile sources that use newer standard-library APIs — e.g. `slices.Collect` / `maps.Keys` (Go 1.23) in `arrow/compute/registry.go`. This surfaced as a failing `RC/Verify (macos-latest)` check: ``` compute/registry.go:143: slices.Collect requires go1.23 or later (file is go1.22) compute/registry.go:143: maps.Keys requires go1.23 or later (file is go1.22) FAIL github.com/apache/arrow-go/v18/arrow/compute [build failed] ``` `RC/Verify (ubuntu-latest)` passed because that runner's preinstalled Go was new enough. ### What changes are included in this PR? Set `GOTOOLCHAIN=auto` on the RC `Verify` step's environment so the Go command honors the `go` directive in `go.mod` and fetches a matching toolchain instead of building with an older preinstalled Go. ### Are these changes tested? This is a CI workflow change, exercised by this PR's own `RC/Verify` jobs. `actionlint` is clean for the modified workflow. ### Are there any user-facing changes? No. CI-only change. -- 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]
