Repository navigation
v1.23.1
Fixed
-
A Windows short-name alias can no longer reach
.git. On NTFS volumes that keep
8.3 short names,GIT~1\objectsis the same directory as.git\objects, and the
.gitboundary only compared names. dev-prune now resolves every deletion target to its
real location first and refuses any that lands inside.git, outside the repository, or
anywhere other than the path that was named. Nothing was known to be hit by this; it was
found in a security review and closed before anyone could be. -
A symlinked or junctioned parent directory can no longer stand in for a prunable
one. The link check only looked at the last path component. It now looks at where the
whole path really leads, for built-in adapters and forprunable.directoriesalike. -
A committed
prunabledeclaration can no longer mark un-ignored files as disposable.
A cloned repository could carry"rebuild": "echo not needed"for a directory holding
your own untracked data. Declared directories now have to be ignored by Git and not
tracked, or they are refused with the reason. If you declare one, add it to
.gitignorefirst. -
devp caches clearrefuses cache paths it cannot vouch for. Cache locations come
from environment variables such asCCACHE_DIRandGOMODCACHE. A value that points at
a filesystem root, at your home directory (or a folder containing it), or at a link is
now left alone and reported. -
devp containers clearwill not act on a remote daemon. An inherited
DOCKER_HOST=ssh://...ortcp://...(orCONTAINER_HOST) used to make "free space on
this machine" prune someone else's engine. The command now stops and says why. Unset the
variable for that command to clear the local engine. -
On Windows, a planted
node.cmdin a repository is no longer picked up.cmd.exe
looks in the current directory beforePATH, and thepnpmandyarnshims call
nodeby bare name. dev-prune now setsNoDefaultCurrentDirectoryInExePathfor the
commands it starts. -
The bundled TLS stack is updated (rustls 0.23.46, rustls-webpki 0.103.16 and
webpki-roots 1.0.11). That closes four rustls advisories and two certificate-trust
advisories (RUSTSEC-2026-0381 and RUSTSEC-2026-0382) in the connection code behind
devp update.
For contributors
- The VS Code extension's icon-font tooling now resolves
glob14 andminimatch11, so
npm auditis clean foreditors/vscode. docs/SAFETY_INVARIANTS.mdnow says plainly that verification runs the package manager
in the repository, and that only npm and bun are passed--ignore-scripts.
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.23.1 / pipx install dev-prune==1.23.1 |
| Rust, no compile | cargo binstall dev-prune@1.23.1 |
| Rust, from source | cargo install dev-prune --version 1.23.1 (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.23.1-windows-x64.zip |
Windows on Intel/AMD — almost every Windows PC |
dev-prune-v1.23.1-windows-arm64.zip |
Windows on ARM — Surface Pro X, Snapdragon laptops, Windows in a Mac VM |
dev-prune-v1.23.1-windows-x86.zip |
32-bit Windows — locked-down corporate images, older industrial machines |
dev-prune-v1.23.1-darwin-arm64.tar.gz |
Apple Silicon Macs — M1 and later |
dev-prune-v1.23.1-darwin-x64.tar.gz |
Intel Macs — 2020 and earlier |
dev-prune-v1.23.1-linux-x64.tar.gz |
Linux on Intel/AMD |
dev-prune-v1.23.1-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.23.1-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.23.1-linux-x64.tar.gz.sha256(Get-FileHash dev-prune-v1.23.1-windows-x64.zip).Hash -eq (Get-Content dev-prune-v1.23.1-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.23.1-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.23.1-linux-x64.tar.gz --repo Life-Experimentalist/dev-prunegh attestation verify dev-prune-v1.23.1-windows-x64.zip --repo Life-Experimentalist/dev-pruneFull Changelog: v1.23.0...v1.23.1