gosd 0.8.2 (2026-08-25)

Features

gosd build accepts go build's own compile flags

gosd build (and gosd-build.toml) now accepts five flags that mirror go build itself, applied to your app's own compile only (never gosd-init):

• --ldflags — e.g. --ldflags="-X main.version=1.4.2" to stamp a version
  into the compiled binary, closing a real gap: until now nothing gosd
  built ever put a version into the app binary itself (--app-version
  bakes into config.json/crash reports only). --ldflags also
  understands one template token, {{.AppVersion}}, substituted with
  --app-version's fully resolved value (including a git: resolution) —
  so --app-version=git:v*.*.* --ldflags="-X main.version={{.AppVersion}}"
  resolves the version once and carries it into both config.json and the
  binary, with nothing to resolve twice.
• --tags — extra Go build tags for your app compile, comma- or
  space-separated. These merge with gosd's own mandatory
  gosd/gosd_<board> tags rather than replacing them; a gosd or
  gosd_-prefixed value is refused, since gosd always adds those itself.
• --trimpath, --gcflags, --asmflags — passed straight through to go build.

None of the five are mirrored on gosd run, matching its existing pattern
of not exposing every build flag. See the build-config docs and
docs/board-build-tags.md for details.

One consequence: gosd build no longer errors on the compile flags tools
like goreleaser's go builder pass by default.
That closes the flag-acceptance gap, but not the rest of the mismatch —
goreleaser's target axis is a {goos}_{goarch} matrix, not gosd's
--board, and -o still means "a bootable disk image," never "one
binary" — so driving a real build still takes some assembly (a builds:
entry per board with filler goos/goarch, or a config-file-read gosd build from a hooks: pre: step instead of tool: gosd).