Repository navigation
v1.19.0
Added
devp updatenow asks before installing. When a newer release exists and you are
at a terminal, the report ends withInstall vX.Y.Z now? [y/N]— Enter leaves the
binary alone,yruns the same download-verify-replace that--installalways did.
The global-yflag answers yes up front, anddevp update --installstill skips
the report entirely. Run from a script or a pipe, nothing changes: the check never
asks and never installs.
Fixed
- The release check no longer reads
api.github.com, whose sixty-requests-an-hour
limit per unauthenticated address could turndevp update(and the passive
update check) into a403that surfaced as "Could not reach the release API".
The version now comes from the redirectLocationof the release page at
github.com/Life-Experimentalist/dev-prune/releases/latest, which has no such
quota — and when the check does fail, the error now prints its full cause chain
instead of a one-line summary. - The install pages taught commands that quietly did nothing on a machine that already
had dev-prune —uv tool install dev-prunereports "already installed" and exits
successfully having changed nothing, and npm, bun, pnpm and yarn share the trap. The
README, the site and the docs now quote the spelling that both installs and updates:
@latestwhere the manager re-resolves it,--forcefor pipx,--upgradefor pip.
For contributors
scripts/bump-version.shnow rewrites the three version strings inSECURITY.md
(the supported-series table row and the twogh attestation verifyexample
filenames), so a version bump no longer failscheck-version.shuntil SECURITY.md
is edited by hand.
Which download do I want?
Most people want none of them. The installers below verify the SHA-256
sidecar, put the binary somewhere already on PATH, and create the devp
alias — three things unzipping an archive does not do.
| You are on | Run this |
|---|---|
| Windows (PowerShell) | iwr -useb https://devprune.vkrishna04.me/install.ps1 | iex |
| Windows (Command Prompt) | powershell -NoProfile -ExecutionPolicy Bypass -Command "iwr -useb https://devprune.vkrishna04.me/install.ps1 | iex" |
| macOS / Linux | curl -fsSL https://devprune.vkrishna04.me/install.sh | sh |
| Python tooling | uv tool install dev-prune==1.19.0 / pipx install dev-prune==1.19.0 |
| Rust, no compile | cargo binstall dev-prune@1.19.0 |
| Rust, from source | cargo install dev-prune --version 1.19.0 (needs Rust 1.88+) |
The PyPI packages contain these same binaries rather than downloading one
afterwards, so they work behind a registry mirror and offline. cargo install
is the only channel that compiles on your machine; cargo binstall reaches
for the archives on this page instead.
Full instructions: https://devprune.vkrishna04.me/#install
The assets, then
Take one only if you are packaging dev-prune yourself, air-gapping it, or
pinning it into a container image.
| Asset | For |
|---|---|
dev-prune-v1.19.0-windows-x64.zip |
Windows on Intel/AMD — almost every Windows PC |
dev-prune-v1.19.0-windows-arm64.zip |
Windows on ARM — Surface Pro X, Snapdragon laptops, Windows in a Mac VM |
dev-prune-v1.19.0-windows-x86.zip |
32-bit Windows — locked-down corporate images, older industrial machines |
dev-prune-v1.19.0-darwin-arm64.tar.gz |
Apple Silicon Macs — M1 and later |
dev-prune-v1.19.0-darwin-x64.tar.gz |
Intel Macs — 2020 and earlier |
dev-prune-v1.19.0-linux-x64.tar.gz |
Linux on Intel/AMD |
dev-prune-v1.19.0-linux-arm64.tar.gz |
Linux on ARM — Raspberry Pi 4/5, Graviton, ARM CI runners |
Both Linux builds are statically linked against musl, so they run on any
distribution including Alpine, with no glibc floor.
32-bit is published for Windows only. There is no 32-bit Linux, no 32-bit
macOS and no 32-bit ARM build on any platform; the install scripts refuse
rather than guess when they meet one.
There is no .vsix on this page. The VS Code extension has its own
version and its own release cadence, so it ships from its own tags:
the extension's releases.
Install it by name instead — VKrishna04.dev-prune, on the
VS Code Marketplace
and on Open VSX.
Windows: the binaries are not code-signed, and two separate features react
to that.
Windows protected your PC is SmartScreen, and it only challenges files
carrying a Mark of the Web — which your browser attaches to the download and
File Explorer copies onto everything it extracts. Clear the mark on the archive
before extracting and nothing inside it is ever marked:
Unblock-File .\dev-prune-v1.19.0-windows-x64.zipThe installers above already do this for you, on the archive and on both
installed copies.
A refusal with no dialog and no "run anyway" is something else: Smart App
Control, which blocks unsigned executables outright and never looks at the mark.
It is on by default on clean installs of Windows 11 22H2+ and always off on
upgraded ones, which is why the same release runs on one machine and not the
next. Unblock-File does not help, and neither does building from source.
The troubleshooting guide
covers what your options actually are.
Every archive ships a .sha256 sidecar. Check it before you trust it:
sha256sum -c dev-prune-v1.19.0-linux-x64.tar.gz.sha256(Get-FileHash dev-prune-v1.19.0-windows-x64.zip).Hash -eq (Get-Content dev-prune-v1.19.0-windows-x64.zip.sha256).Split(' ')[0].ToUpper()An archive's hash stops meaning anything the moment you unpack it, and the
unpacked files are the only ones your antivirus ever looks at. So each Windows
zip also ships a .zip.contents.sha256 listing the digest of every file inside
it — run this in the folder you extracted to, from Git Bash (sha256sum ships
with Git for Windows, and is what reads this format):
sha256sum -c dev-prune-v1.19.0-windows-x64.zip.contents.sha256dev-prune.exe and devp.exe are one file under two names and share a digest
on purpose, so a scanner builds one reputation record instead of two.
devpw.exe — the console-free build the scheduled task runs — is compiled
separately and legitimately has a different one. devp trust prints the same
three digests for the copies already installed on your machine, so you can
compare them against this file without downloading anything again.
That sidecar proves the file was not altered in transit. It does not prove
where it came from — the same hand that swaps an archive swaps its sidecar.
Every archive on this page is also signed by GitHub's build provenance, which
binds it to this repository, this workflow and the commit it was built from:
gh attestation verify dev-prune-v1.19.0-linux-x64.tar.gz --repo Life-Experimentalist/dev-prunegh attestation verify dev-prune-v1.19.0-windows-x64.zip --repo Life-Experimentalist/dev-pruneWhat's Changed
- ci: bump softprops/action-gh-release from 3.0.2 to 3.0.3 in the actions-minor-and-patch group by @dependabot[bot] in #29
- deps(site): bump @types/react-dom from 19.2.4 to 19.2.5 in /site in the site-minor-and-patch group by @dependabot[bot] in #28
New Contributors
- @dependabot[bot] made their first contribution in #29
Full Changelog: v1.18.0...v1.19.0