release: version flag, tagged binary releases, systemd unit#38
Merged
Conversation
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 "single static binary" story gets its last mile: a way to know what you are running, a place to download it, and a unit to run it under.
sandboxd -version: stamped via-ldflags -X main.version(make sandboxdusesgit describe --match 'v*', so SDK tags don't leak in); untagged builds fall back to the Go-embedded VCS revision. The version is also logged once at startup, so journals identify the running build.release.yml: av*tag builds static linux/amd64sandboxd+sandbox-mcp(CGO_ENABLED=0 -trimpath -s -w), writesSHA256SUMS, and publishes a GitHub release with generated notes. SDK packages keep their separatesdk-*-v*→ PyPI path.packaging/sandboxd.service: the minimal unit from deploy.md, shipped as a file; deploy.md now points at releases and the unit.Hot-path cost: zero — a startup log line and a flag.
Evidence:
make sandboxd && dist/sandboxd -version→sandboxd 6615de0-dirty(VCS fallback path, no v* tag yet); module tests green; dual-GOOS lint 0 issues; the workflow first fires on the firstv*tag.