0.27.1
A one-command install, and a beginner's path through the docs. No library or command behaviour
changed in this release — prikk itself is byte-for-byte the same tool as 0.27.0. This cut exists
so the installer has a release to attach to.
Added
-
A shell installer and uninstaller, attached to this release as
install.shanduninstall.sh
with their own checksums:curl -fsSL https://github.com/nabbisen/prikk/releases/latest/download/install.sh | shIt detects the platform, downloads the matching archive, verifies its SHA-256 and refuses to
install if verification fails or if no checksum tool is present, and puts the binary onPATH.
--version X.Y.Zpins a release;--prefix DIRchooses the location. The download-then-inspect
form is documented beside the pipe form.uninstall.shremoves the binary and the one marked
PATHblock it added, and nothing else. Linux (x86_64/aarch64) and macOS (Apple Silicon);
Windows is refused with a message pointing atcargo installor the.zip.What a passing checksum proves is integrity of transport, not authority of origin —
release-signers.tomlis still empty and fail-closed, so no release yet satisfies the DC-35
signer-authority audit. The installer says so itself when it finishes. -
A beginner's on-ramp in the documentation — a tutorial,
a troubleshooting page, and an
FAQ, placed before the signing setup a reader
previously met first. The tutorial's commands are run by a test on every change, so a release
that breaks them fails CI rather than the reader. -
Build-from-source guidance for platforms without a prebuilt binary — other Linux architectures
build with no reduction in capability; the BSDs compile but are read-only, since repository
mutation is refused off Linux, macOS, and Windows.
Fixed
Nothing — no behaviour changed.
Prebuilt binaries
Linux (aarch64/x86_64), Windows (x86_64), macOS (aarch64). Each archive contains the prikk binary, LICENSE, and a sibling .sha256
checksum plus .build-info.txt recording the exact toolchain and command used to build
it — reproduce with:
git checkout <tag> && cargo build -p prikk --release --target <triple> --lockedcargo install prikk remains the toolchain-based install path; these binaries are an
additional option, not a replacement.
macOS binaries are unsigned. Gatekeeper will warn on first run — right-click (or Control-click) the binary and choose Open, or clear the quarantine attribute directly with xattr -d com.apple.quarantine <path>. Notarization needs an Apple Developer identity and is a stated gap for a future increment, not an oversight.
Release authority — read before relying on this release
This release does not pass the DC-35 signer-authority audit, and does not claim to. The
committed release-signer set (release-signers.toml) is empty and fail-closed, so no release
currently satisfies that gate. A checksum published beside a binary on this page proves integrity of
transport, not authority of origin. Verify what you obtain by content, not by release authority —
see prikk verify and this project's
release-compatibility reference.