v0.6.2

v0.6.2 — v0.6.2 — distributable source, and a lockfile worth trusting

This is a packaging release: no behaviour changed, but the project can now be installed from a source tarball without resolving a moving dependency graph.

crates.io-ready workspace

The internal gander dependencies now carry a version alongside their path, which cargo requires before it will package any of the four crates. The executable is published as gander-bin because the gander crate name was taken by an unrelated, yanked project in 2024; cargo install gander-bin still installs a binary named gander.

Cargo.lock is committed. The v0.6.1 source archive did not contain one, so cargo build --locked failed before compiling a line and Homebrew or AUR recipes could not pin the dependency graph. The same archive now builds reproducibly with the lockfile that CI and local tests use.

README and docs/RELEASING.md now describe the four-crate publish order and the lockfile rule, so the next release cannot silently regress either one.

Packaging recipes

packaging/ contains a Homebrew formula, an AUR PKGBUILD with .SRCINFO, and the checksums and commands needed to submit them. All point at the annotated v0.6.2 tag; the distribution metadata lives with the source rather than only in a tap or an AUR repository.

Tests: 145 core, 33 config, 151 TUI, plus integration and doc tests; cargo clippy --workspace --all-targets -- -D warnings is clean. The full suite runs outside the macOS sandbox, which denies KERN_PROC_ALL.

---

Install

tar -xzf gander-0.6.2-<platform>.tar.gz
./gander-0.6.2-*/gander

Archive	Platform
aarch64-apple-darwin	macOS, Apple Silicon
x86_64-apple-darwin	macOS, Intel
x86_64-unknown-linux-gnu	Linux (glibc)
x86_64-unknown-linux-musl	Linux (static, any distro)
x86_64-unknown-freebsd	FreeBSD 14 and later

Every archive has a .sha256 beside it: shasum -a 256 -c <file>.sha256.
From source: cargo install --path crates/bin (Rust 1.89+).

Full history: commits

Every release is explained at length — the reasoning, the alternatives, and what a
live kernel or VM taught the implementation — in
docs/ROADMAP.md. The notes above say
what shipped; ROADMAP says why.