Repository navigation
NurCLI v0.43.2
NurCLI v0.43.2 - verified updates
A bug and parity pass over the whole codebase, docs and site. Clippy is clean with and without default features; all unit tests, the E2E suite and the regression and startup suites pass.
Updates are checked against the published checksum
- The self-updater (
nur updateand the launch check) now compares every download with the<asset>.sha256each release publishes and refuses a mismatch before anything touches disk. - The updater no longer treats
.tar.gzassets as installable. It had accepted gzip bodies as executables and would have written an archive straight overnur, and its fuzzy asset match could reach archive or checksum files. - SHA-256 hashing runs in process instead of launching
certutil/shasum(the updater, the impostor scrub andnur doctorused two copies of that code).nur doctornow reads the install record fromNUR_INSTALL_DIRwhen it is set.
npm shim (npx nur-cli)
- Verifies the published checksum, writes beside the target and renames, and says plainly when a running
nurholds the file. - Its fallback download is the package's own release instead of a stale v0.40.1 pin.
Install and docs
install.ps1honorsNUR_CLI_DIR, asinstall.shand the README already did; theirm | iexone-liner cannot pass-RepoDir.- The docs site no longer publishes verbatim third-party page and paper captures (
docs/research/_extracts) or internal agent plans; pages kept out of the nav on purpose are marked as such.