From 061f1d6d7ea1b2df0e337df84b354c500efae5cc Mon Sep 17 00:00:00 2001 From: Julian Goldstein Date: Fri, 19 Jun 2026 13:01:30 -0500 Subject: [PATCH] docs: describe semver versioning in versions.env [bump:minor] Demo of the new versioning flow: this build/ change triggers vendor-toolchain on merge, which (unmarked default / explicit [bump:minor]) bumps the highest clean tag v0.5 to v0.6.0. No fingerprinted build input changed, so every tool is reused from the v0.5 release. Co-Authored-By: Claude Opus 4.8 --- build/versions.env | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/build/versions.env b/build/versions.env index 0db349e..45e8061 100644 --- a/build/versions.env +++ b/build/versions.env @@ -4,7 +4,9 @@ # Toolchain bundle version. Each publish is an immutable, version-tagged # release `v` holding the whole set; consumers pin this one # number, and the cache is keyed by it (cache/yeet/toolchain/v//). CI -# bumps it by 0.1 on every publish (which only happens when build/ changes). +# computes it as semver (vMAJOR.MINOR.PATCH) from the [bump:*] markers on the +# commits since the last release (default minor); see the README. Republished +# only when build/ changes. TOOLCHAIN_VERSION=0.1 # Where a consumer fetches assets from: the version-tagged release. The fetch