You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[CHORE] Move the MCP Go launcher off Go 1.25 and retire or update goreleaser.yml (Go 1.16) #860
Housekeeping left over from #857 after v0.12.813 ships. Neither item changes what users download today; both leave a workflow on a Go line that never received the eMudhra crypto/x509 fix.
1. MCP Go launcher is built with Go 1.25
.github/workflows/mcp-packaging.yml, sdk job, matrix.vector == 'go': actions/setup-go@v6 with go-version: '1.25'. packaging/mcpb/go/go.mod says go 1.25.0. Go 1.25 is out of support (current lines are 1.27 and 1.26), so it stays without the fix for good. The launcher's only network call is the HTTPS fetch of the stackql bundle from releases.stackql.io, verified against sha256 pins in its embedded manifest, so the worst case is a failed download, not a substituted binary.
Fix: go-version: '1.27.3' (the other setup-go in the same workflow already is), go 1.27.3 in packaging/mcpb/go/go.mod, rerun make go-build and the smoke test.
2. goreleaser.yml pins Go 1.16
Triggers on release* tags with actions/setup-go@v2 and go-version: 1.16. It cannot build current code (go.mod requires 1.27.3) and docs/stackql_release_process.md does not use it. Delete it, or if it is wanted as a fallback, move it to actions/setup-go@v7 with go-version-file: go.mod.
Done when
No workflow in the repo references a Go version below 1.26, and the Go launcher bundle builds and passes its smoke test on 1.27.3.
Activity