Shelly ALPM v3.0.6 Ships Valgrind Integration and Leak Fixes for the New Arch Package Manager
Seafoam Labs released Shelly ALPM v3.0.6 on August 14, and if you are wondering what actually changed, it is exactly what you would want for a system-level tool: the CI pipeline now runs Valgrind, and the team patched the memory leaks that tooling uncovered.
Keep in mind that Shelly has never been a pacman wrapper. It talks directly to libalpm, pairs that with a GTK4 frontend, and runs as a single Zig binary. That architectural choice became even more deliberate back in late July when the v3.0.0 rewrite shipped. The team gutted hundreds of lines of C# and .NET code, rebuilding the core, the CLI, the keyring tool, and the desktop app from scratch. Nine releases in thirty days. Valgrind integration has been one of the quiet questions about Shelly since the Zig rewrite began. The team finally answered it.
What You Actually Get in 3.0.6
The release contains eight merged pull requests from five contributors, including one brand new face on the project. The real work came from @caroberrie, who added a Valgrind build step to the CI pipeline, wrote GTK suppression files, and set up log file infrastructure for long-form memory analysis. They also fixed the tiny heap leaks that runner caught. Meanwhile, @azdanov cleaned up TryExec entries in the .desktop file and fixed submenu ID handling so the menus actually behave correctly in GNOME and KDE Plasma.
The team also added scripts/bump-version.sh, which means future releases will not require manual grep sessions across twenty-one files.
Head here to the GitHub repository if you want to track the ongoing development.
Why Zig Still Matters Here
The shift away from .NET was never just about dropping a runtime dependency. It was about predictable memory lifetimes and compile-time checks right at the C library boundary. libalpm, GTK4, libarchive, GPG. Zig gives Shelly one native build and test workflow for the CLI, UI, keyring, and optional Flatpak backend. The Flatpak layer stays opt-in and separately packaged, which keeps the base install lean for users who do not touch third-party software.
It is a maintenance release, so do not expect shiny new buttons. That is actually the best kind of update for a package manager. When your tool is quietly scanning your /var directory and potentially breaking your system on a bad dependency, you would rather hear about memory hygiene than feature bloat. The Flatpak backend remains opt-in and the base install stays tight. If you are on CachyOS, it is already in the repos. Otherwise, grab it from the AUR with yay -S shelly or paru -S shelly.
