Repository navigation
[yumin-xia] ci: release binaries for five platforms with checksums and an install script - #21
Merged
Merged
Conversation
… script Releases had no binaries; only make build from a clone reported the right version. A tag push (or a manual run for an existing tag) now builds sqlc for linux/amd64, linux/arm64 (static, CGO, musl), darwin/amd64, darwin/arm64 (CGO, macOS 12+) and windows/amd64 (no CGO), runs each on its own platform, and attaches the archives, checksums.txt and build provenance to the release. scripts/install.sh installs a release after checking its SHA-256. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Stumble
force-pushed
the
yumin-xia/release-binaries
branch
from
November 4, 2026 08:13
0355447 to
069691c
Compare
v2.4.0's source has the dependencies govulncheck flagged (#22), so binaries start with v2.4.1. Install examples point to it; add its release notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases had no binaries. Only
make buildfrom a clone reports the right version;go install ./cmd/sqlcreportsv1.31.1, which ended up in generated headers downstream (ggsrc/ggsrv-layout)..github/workflows/release.yml: on a tag push, or run by hand for an existing tag, builds linux/amd64 and linux/arm64 (CGO, static musl, any distribution), darwin/amd64 and darwin/arm64 (CGO, macOS 12+), windows/amd64 (no CGO). Each binary runssqlc version,compileandgenerateon its own platform; then the archives,checksums.txtand build provenance are attached to the release, andscripts/install.shinstalls it on Linux and macOS runners.scripts/install.sh: picks the platform, downloads the archive, checks its SHA-256 (SQLC_SHA256or the release'schecksums.txt), installs into$(go env GOPATH)/bin.CGO and non-CGO builds generate identical code (wicked_compat, ggsrv-layout, bookstore); CGO runs take ~60 ms, the WebAssembly parser ~2.2 s.
Changelog:
docs/changelogs/2026-11-04-release-binaries.md. v2.4.0 keeps the dependencies fixed in #22, so the first binaries ship as v2.4.1: install examples point to it anddocs/releases/v2.4.1.mdholds its notes. After merging, pushing thev2.4.1tag builds and publishes it.🤖 Generated with Claude Code