You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[outreach] README install, cosign and Status examples still pin v0.3.0 after v0.4.0 shipped #133
Type: adoption (install path) Target: people installing Crux from the README
v0.4.0 was published on 2026-11-08 (release). The README still points every pinned install example at v0.3.0:
docker run --rm ghcr.io/hivecommons/crux:0.3.0 --help (Install)
the cosign + checksum walkthrough: "from the v0.3.0 release page", crux_0.3.0_linux_amd64.tar.gz, crux_0.3.0_darwin_arm64.tar.gz
cosign verify ghcr.io/hivecommons/crux:0.3.0
Status: "Current release: v0.3.0."
The other install paths already give v0.4.0. brew install hivecommons/hive/crux resolves to v0.4.0: Formula/crux.rb in homebrew-hive downloads the v0.4.0 archives. go install ...@latest resolves to v0.4.0 too. So a container or archive user following the README gets an older build than a brew or go user does, and the README calls the older build current.
Why Now
v0.4.0 is the first release after the README links the community meeting (#116), documents the lanes surface (#113) and counts cline (#111). Someone who pulls the 0.3.0 image the README names doesn't get the build those sections describe. #109 fixed the same drift for v0.3.0. Nothing updates this string automatically.
Proposed Action
Replace each 0.3.0 / v0.3.0 in README.md (7 sites) with 0.4.0 / v0.4.0. All are verified against the release: the four crux_0.4.0_{darwin,linux}_{amd64,arm64}.tar.gz archives, checksums.txt, checksums.txt.sigstore.json and ghcr.io/hivecommons/crux:0.4.0 are all published.
Activity