Problem
The VERSION file in the repository still contains v0.6.2, but the latest git tag and GitHub release is v0.6.4. This causes locally built binaries to report incorrect version information.
$ cat VERSION
v0.6.2
$ git describe --tags
v0.6.4-5-g11ab228
$ go run main.go --version
crdoc version v0.6.2
Root Cause
The VERSION file was designed to be updated automatically by the GitHub Actions workflow (.github/workflows/tag.yml), but this process was not followed for releases v0.6.3 and v0.6.4.
What Happened
For v0.6.3 and v0.6.4, tags were created manually on existing commits
Impact
- ✅ GitHub releases: May show correct metadata
- ❌ Local builds (
go build, go run, go install): Report v0.6.2 instead of v0.6.4
- ❌ Repository state: Out of sync with release tags
- ❌ Developer experience: Confusion about actual version
The issue affects anyone building the tool from source, as main.go embeds the VERSION file at build time:
//go:embed VERSION
var version string
Problem
The
VERSIONfile in the repository still containsv0.6.2, but the latest git tag and GitHub release isv0.6.4. This causes locally built binaries to report incorrect version information.Root Cause
The VERSION file was designed to be updated automatically by the GitHub Actions workflow (
.github/workflows/tag.yml), but this process was not followed for releases v0.6.3 and v0.6.4.What Happened
For v0.6.3 and v0.6.4, tags were created manually on existing commits
Impact
go build,go run,go install): Report v0.6.2 instead of v0.6.4The issue affects anyone building the tool from source, as main.go embeds the VERSION file at build time: