an opinionated terminal multiplexer in C with programmable pane chrome https://git.sl0p.foo/slosh.git/atom/VERSION?h=docs-new 2026-08-28T13:43:57Z 2026-08-28T13:43:57Z user user@clank 2026-08-28T13:43:57Z urn:sha1:25e5decae660ebc41dbdc656a47715df2f855212 The floor contrib/version falls back to without git -- a cgit snapshot, a Homebrew source build -- still said 0.1.0 after v0.1.1 was tagged, so those builds reported a version that was already released. The tag and the file are two steps, and nothing made them one; contrib/release now does. 2026-08-26T23:22:34Z user user@clank 2026-08-26T23:22:34Z urn:sha1:276ea2610c783bd61789691b910b4be4dbeae890 VERSION was a constant in the Makefile that had to be bumped by hand and could silently disagree with the git tag a release was cut from. Derive it instead, with a committed ./VERSION as the floor and no-git fallback: on a tag v0.2.0 -> 0.2.0 past a tag v0.2.0-5-gabc123 -> 0.2.0-5-gabc123 (sorts after 0.2.0) before any tag 0.1.0-197-g2d1815 -> ./VERSION + commit count + short id no .git at all 0.1.0 -> ./VERSION verbatim (cgit snapshot -> Homebrew source build) A dirty tree appends -dirty. The commit count keeps 'brew upgrade' ordering monotonic before the first tag exists. version.h now bakes just VERSION (dropping the redundant +GITDESC, which the derived string already carries). contrib/brew-release reads the base from ./VERSION rather than grepping the Makefile's VERSION line, which is now a $(shell ...) expression it could not parse.