Skip to content

fix(version): report sluice's own version, not an enclosing repo's (v0.1.1)#13

Merged
Pyronewbic merged 1 commit into
mainfrom
v0.1.1
May 31, 2026
Merged

fix(version): report sluice's own version, not an enclosing repo's (v0.1.1)#13
Pyronewbic merged 1 commit into
mainfrom
v0.1.1

Conversation

@Pyronewbic

Copy link
Copy Markdown
Owner

Cutting v0.1.1 to fix a version-reporting bug the Homebrew install surfaced.

Bug: sluice_version() ran git describe at the install dir, but git walks up for a .git - and a brew install lives inside /opt/homebrew (a git repo), so sluice -v reported Homebrew's version (5.1.14) instead of sluice's. Now it only trusts git when $ROOT is sluice's own checkout (.git present), else the baked SLUICE_VERSION. Verified: a no-.git install nested in another git repo now reports the baked version.

Also: baked version -> 0.1.1; brew install Pyronewbic/tap/sluice added to the README (the tap repo is now live); the in-repo formula is marked a template (the tap holds the sha-pinned formula).

After merge: tag v0.1.1 -> release, then pin the tap formula to the v0.1.1 sha.

…0.1.1 + brew

`git describe` at the install dir walked up to an enclosing git repo (e.g. Homebrew's
/opt/homebrew), so a brew-installed `sluice -v` reported Homebrew's version. Only trust git
when $ROOT is sluice's own checkout (.git present), else the baked SLUICE_VERSION.

Also bump the baked version to 0.1.1, add `brew install Pyronewbic/tap/sluice` to the README
(the tap is now live), and mark the in-repo formula a template (the tap is the source of truth).
@Pyronewbic Pyronewbic merged commit f1d3c96 into main May 31, 2026
3 checks passed
@Pyronewbic Pyronewbic deleted the v0.1.1 branch May 31, 2026 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant