build: license, goreleaser release pipeline, and CI - #1
Merged
Conversation
The CLI is documented as a first-class component of the platform but carried no license file, which means all rights reserved by default. Same MIT text as the platform repo. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The CLI is documented as a first-class component of the platform but had no release tooling and no CI at all: the only way to get a binary was `go build -o stone`, which meant every user compiled their own and `--version` reported "dev". goreleaser builds six targets from one runner (nothing needs cgo) and stamps cmd.version, so an installed `stone` can say what it is. windows/arm64 is included here and excluded in the platform on purpose: this is a laptop and CI-runner tool. CI cross-compiles the whole release matrix on every pull request, so a broken target is found before a tag is pushed rather than by goreleaser failing on it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
skeeeon
marked this pull request as ready for review
August 22, 2026 19:52
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
1 participant
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.
The CLI is documented as a first-class component of the platform (a 407-line chapter, the longest page on the docs site) but had no license, no release tooling and no CI. The only way to get a binary was
go build -o stone, so every user compiled their own and--versionreporteddev.LICENSE— none previously, which means all rights reserved by default..goreleaser.yaml— six targets from one runner (nothing in the tree needs cgo), stampingcmd.version.windows/arm64is included here and excluded in the platform on purpose: this is a laptop and CI-runner tool, and ARM Windows laptops exist; a server binary has no such audience. Archives carryLICENSE,README.mdandSKILLS.md.ci.yml— gofmt gate, vet, test, build, plus a cross-compile of the whole release matrix on every PR, so a broken target is found before a tag is pushed rather than by goreleaser failing on it.release.yml— tests, then goreleaser on av*tag.Verified end to end locally: extracted the built linux/amd64 archive and ran it —
stone version 0.0.0-SNAPSHOT-4695e37, so the stamp reaches the shipped binary.🤖 Generated with Claude Code