cargo-nextest gets install scripts after four and a half years, in a change of 10,000 lines
cargo-nextest, the Rust test runner, now ships install scripts, its maintainer wrote on the sunshowers blog on 14 November. It is four and a half years since the first release. On Unix-like systems, including WSL, Cygwin and Git Bash on Windows, the command is curl -LsSf https://get.nexte.st/install.sh | sh; in PowerShell it is irm https://get.nexte.st/install.ps1 | iex.
The project has published release binaries since 2022, but the maintainer had decided against scripts at the time. Separate Unix and Windows scripts are hard to write and to test across many situations, and many users dislike piping a download into a shell. Instead, users were asked to extract a tarball, or a zip on Windows, themselves. The short URLs sit behind a redirect service, first Netlify and now Cloudflare; the binaries are built in GitHub Actions, hosted on GitHub Releases and not changed after publication, which GitHub's immutable releases now attest. A small release manager called mukti handles it.
That approach showed limits. The Windows instructions ran to five lines, there was no single command for the home page, and on Linux nothing picked the statically linked musl build when the system glibc was too old or missing.
The new scripts start from an install manifest that mukti now writes for every version, a text file of archive URLs and checksums at https://get.nexte.st/<version>/install-manifest.txt. The version can also be a series such as 0.9, or latest. A script downloads the manifest, inspects the machine, downloads the best candidate, checks its checksum and extracts the binary. The shell script works with any Bourne shell; the PowerShell script runs on both 5.1 and 7. Edge cases include the musl fallback, defects in the bash 3.2 that macOS uses as its default sh, and shells emulated on another architecture, such as x86_64 Git Bash on aarch64 Windows, where the scripts install the native build.
Claude Code and Codex did much of the implementation and testing. The harness runs dozens of cases on several shells, with an HTTP server behind TLS, a helper binary that injects faults and tests for truncated scripts and interrupted downloads. Manual review then found problems the agents had not: there was no test for the basic default install, SHA-256 hashes were compared as case-insensitive strings, the scripts allowed HTTPS-to-HTTP redirects and the tests checked that they worked, and Windows had no Ctrl-C tests. Redirects to HTTP are now banned. The review took about 25 hours over four weekends, and the final change is around 10,000 lines, most of it tests. Extracting the archive by hand still works.

Why it matters
For nextest users the change is a single install command on every platform. The more general point is in the redirect bug: the maintainer writes that once a model encoded the wrong behaviour in the test suite, later automated reviews by other models took the passing tests as evidence that it was intended. Only the human review caught it.