feat: packaging + signed release pipeline; v0.1.0 quickstart - #9
Merged
Conversation
The single-binary, one-line docker run finish for v0.1. - Dockerfile: cross-compiled (no QEMU tax), pure-Go static binary on distroless static nonroot; /data volume; runs as 65532. .dockerignore keeps the build context lean and secret-free. - .goreleaser.yaml: multi-arch (linux/darwin, amd64/arm64) binaries, archives, checksums; GitHub release notes from conventional commits; version stamped into internal/version via ldflags. - .github/workflows/release.yml (on v* tags): GoReleaser binaries + release; multi-arch image to GHCR built from the main Dockerfile and cosign-signed keyless via OIDC (id-token write). v* tags are admin-only (tag ruleset). - Makefile: build/test/vet/fmt/vuln/check/sdk-test/docker/run targets. - README: real 60-second quickstart (docker run -> one env var -> governed call with cost headers -> 402 on budget); release badge. - CHANGELOG: cut the 0.1.0 section. Definition of done (v0.1) met: zero-code adoption via one env var; the governor hard-stops every budget; a SIGKILL'd run resumes from its checkpoint; steps/ tools/tokens/cost are visible locally and exportable as OTel; side effects require approval; nothing phones home.
prashar32
changed the title
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.
What & why
The packaging finish line for v0.1 (§8 step 11): single binary, one-line
docker run, and a signed release pipeline./datavolume..dockerignorekeeps the context lean and secret-free..goreleaser.yaml— multi-arch binaries (linux/darwin, amd64/arm64), archives, checksums, GitHub release notes; version stamped via ldflags.release.yml(onv*tags) — GoReleaser binaries + release; multi-arch image to GHCR built from the main Dockerfile and cosign-signed keyless (OIDC).v*tags are admin-only via the tag ruleset.build / test / vet / fmt / vuln / check / sdk-test / docker / run.0.1.0section.Definition of done (v0.1) — all met
SIGKILL'd run resumes from its checkpoint ✓Verification
go test -race ./..., Python SDK suite,vet,gofmtall green.make buildstamps version via ldflags. (Docker image + cosign run on thev*tag.)v0.1.0is tagged separately after this merges (tagging triggers the signed release build + GHCR image)