Summary
ktext version is hardcoded and can drift from the actual release tag.
Evidence
cmd/ktext/main.go currently hardcodes const version = "0.1.0"
.goreleaser.yaml strips binaries but does not inject version metadata from tags via ldflags
Actual behavior
A tagged release can still produce a binary that reports the hardcoded version instead of the tag that built it.
Expected behavior
Release binaries should report the actual git tag / release version.
Why this matters
Incorrect version output makes support/debugging harder and weakens confidence that a user is actually running the expected release artifact.
Summary
ktext versionis hardcoded and can drift from the actual release tag.Evidence
cmd/ktext/main.gocurrently hardcodesconst version = "0.1.0".goreleaser.yamlstrips binaries but does not inject version metadata from tags vialdflagsActual behavior
A tagged release can still produce a binary that reports the hardcoded version instead of the tag that built it.
Expected behavior
Release binaries should report the actual git tag / release version.
Why this matters
Incorrect version output makes support/debugging harder and weakens confidence that a user is actually running the expected release artifact.