release-prep: bump VERSION to 0.1.2 (missed v0.1.1 bump)#14
Merged
Conversation
The internal/project/VERSION file controls what `cascade --version` reports for proxy-installed binaries (via //go:embed). v0.1.1 shipped without bumping this file — the v0.1.1 binary installed via `go install ...@v0.1.1` reports "cascade 0.1.0" instead of "cascade 0.1.1". The bug fix that motivated v0.1.1 (issue #12) is correct and shipped; only the version self-report is stale. Bumping to 0.1.2 (skipping 0.1.1 since that tag already exists). On release of v0.1.2, the proxy-installed binary will correctly report "cascade 0.1.2". Verified: ./bin/cascade --version (make-built, ldflags injection active) reports "cascade 0.1.2 (build release/v0.1.2-version-bump@ e0c1477, 2026-05-07T21:51:28Z)". A future v0.2 enhancement should consume runtime/debug.ReadBuildInfo's BuildInfo.Settings (vcs.revision, vcs.time) for proxy installs so the build metadata is non-N/A even without ldflags injection. Tracked informally in the M5 retro carry-forward. Lessons learned for future release prep: add an explicit internal/project/VERSION-vs-tag-version check to the release flow (either in the Makefile's release-dry-run target or in a pre-tag checklist) so this doesn't recur. Tracked for v0.2 release-prep. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
What
One-line bump of
internal/project/VERSIONfrom0.1.0to0.1.2. Skips0.1.1because that tag is already cut.Why
We forgot to bump
internal/project/VERSIONas part of the v0.1.1 release prep. The result:go install github.com/geomyidia/cascade/cmd/cascade@v0.1.1produces a binary that reportscascade 0.1.0 (build N/A)— the version self-report is one minor behind. The actual bug fix that motivated v0.1.1 (issue #12) is correct and works; only the--versionoutput string is stale.How it works
internal/project/VERSIONis read two ways:make build-built binaries — read at build time via the Makefile'scat internal/project/VERSIONand injected via-ldflags -X. Make builds always reflect the current VERSION file.go install-built binaries — read at runtime via//go:embed VERSIONinsideinternal/project/version.go. Proxy installs only see whatever's committed to the tagged ref.The proxy-install path is the one that bit us: v0.1.1 was tagged with
internal/project/VERSION=0.1.0, so every proxy-installed v0.1.1 binary reports0.1.0.Verification
After the bump:
After v0.1.2 ships, proxy-installed binaries will report
cascade 0.1.2 (build N/A)correctly. (The(build N/A)part for proxy installs is a separate v0.2 enhancement; tracked in the M5 retro carry-forward.)Checklist
make checkpasses locally (no behaviour changes)make build && ./bin/cascade --versionBreaking change?
No. Cosmetic fix to the version self-report. v0.1.1's bug-#12 fix is unaffected.
Lessons learned (for v0.2 release-prep)
We need an explicit
internal/project/VERSION-vs-tag-version check before tagging — either:Makefile'srelease-dry-runtarget (comparecat internal/project/VERSIONto$(VERSION)minus thevprefix); orTracked informally for v0.2 release-prep.
🤖 Generated with Claude Code