From c0b02c336e94ee6c633ac75c7f21b4cc5f5748a9 Mon Sep 17 00:00:00 2001 From: Duncan McGreggor Date: Thu, 7 May 2026 16:51:59 -0500 Subject: [PATCH] release-prep: bump VERSION to 0.1.2 (missed v0.1.1 bump) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- internal/project/VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/project/VERSION b/internal/project/VERSION index 6e8bf73..8294c18 100644 --- a/internal/project/VERSION +++ b/internal/project/VERSION @@ -1 +1 @@ -0.1.0 +0.1.2 \ No newline at end of file