ingitdb / ingitdb-cli / 33369740986

96%

push

github

fix: adopt strongo/buildinfo for unified version reporting (#137)

`ingitdb --version` and `ingitdb version` independently disagreed:
fang's own debug.ReadBuildInfo() fallback printed "unknown (built from
source)" for the flag, while the hand-rolled `version` subcommand read
main.version/commit/date (only main.version was ever ldflags-stamped by
.goreleaser.yaml, so commit and date were always their zero defaults).

Adopt the fleet's shared github.com/strongo/buildinfo@v0.1.0 module so
both surfaces resolve from the identical Info value:
- main.go now calls buildinfo.Get("ingitdb") and cobracmd.Wire(root, info),
  feeding the returned fang.Option into fang.Execute instead of leaving
  fang to fall back on its own build-info guess. SelfUpdate now receives
  info.Version (bare semver) instead of the old package-level var.
- cmd/ingitdb/commands/version.go (and its test) is deleted; cobracmd
  supplies the `version` subcommand now.
- .goreleaser.yaml, .github/goreleaser-chocolatey.yaml and
  .github/goreleaser-snap.yaml all build the same ./cmd/ingitdb main
  package, so all three are switched from the single
  `-X main.version={{.Version}}` ldflag (which would no longer link,
  since main.version doesn't exist anymore) to buildinfo's canonical
  three-line snippet targeting github.com/strongo/buildinfo.{version,
  commit,date}.

Verified with a real ldflags build: --version and version now report the
identical stamped version, and an unstamped `go build` degrades to
buildinfo's runtime/debug.ReadBuildInfo() fallback without panicking.


Claude-Session: https://claude.ai/code/session_01KFsyYhYi9h9Am1JbAMxuhv

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

5 of 5 new or added lines in 1 file covered. (100.0%)

5240 of 5443 relevant lines covered (96.27%)

0.97 hits per line