Shelly ALPM v3.0.3 Shipped Today, Continues Post-Rewrite Stabilization Push
Shelly ALPM v3.0.3 landed this morning, wrapping up roughly 35 merged pull requests on top of a major architectural overhaul that dropped just one week ago. The maintenance release brings cache management tweaks, experimental aarch64 support, UI hotkeys, and a redesigned transaction page. If you've been watching the v3.x line from the sidelines, this is the point where the rewrite stops looking like a prototype and starts feeling like a real package manager.
The project, maintained by Zoey Erin Bauer at Seafoam Labs, links directly to libalpm instead of wrapping pacman. That distinction matters to Arch users who have watched other so-called modern package managers quietly shell out to the terminal under the hood. By talking straight to the same C library pacman uses, Shelly skips the interop overhead entirely. The old C# and .NET codebase from the v2.x line has been completely retired, replaced by a clean Zig foundation that compiles directly to native executables.
The Changelog and The Cadence
This release is mostly stabilization work rather than a feature dump. Beyond the aarch64 flag and cache management changes, the team patched dropdown selection logic, fixed a Flatpak window width bug, and added a new Basque translation alongside updates to Greek, Polish, German, Japanese, Russian, and Portuguese. The flatpak backend also gets better handling for user-scoped installations.
If you're keeping score, that's one release a day for the first week of the v3.x line. v3.0.0 arrived on July 29, followed by incremental hotfixes through August 2 before today's batch. The rapid pace is normal for a ground-up rewrite, though it does mean the Flatpak backend ABI and the clean-chroot AUR builder are still being hardened. The core libalpm logic appears stable enough to ship, which is the main thing.
Six Components, One Build
Shelly now runs as six distinct modules bundled under a single repository. The GTK4 desktop app handles the visual layer, while the CLI powers terminal workflows. A standalone HTTP client manages repository fetches, and a separate notification tray service handles desktop alerts. The package manager core ties it all together, and Flatpak support lives in its own module that communicates through a versioned native ABI.
That separation is intentional. The base CLI no longer links to libflatpak, GLib, or OSTree. You can skip the backend package entirely if you don't use Flatpak. ALPM, AUR, AppImage, and standard repository operations all function without it. Shelly checks the ABI version before loading the module and will reject an incompatible backend cleanly rather than crashing mid-operation.
Keep in mind that the CLI has been rebuilt from the ground up, so automation scripts built for v2 will need auditing against the new shelly --help output. The tradeoff is real though: no garbage collector kicking in during a long upgrade, predictable memory lifetimes for multi-gigabyte transactions, and compile-time binding checks at the libalpm boundary.
Community reaction has been mixed but mostly positive. Early adopters on r/archlinux have praised the unified experience across system packages, AUR, Flatpaks, and AppImages. Skeptics point out that building a non-pacman wrapper is inherently risky for a distro that runs on pacman under the hood. However, at the same time, the migration from .NET to Zig addressed the heaviest criticism of the v2 line, even if formal benchmark comparisons between the old runtime and the new Zig builds are still pending.
Where To Get It
CachyOS users get it shipped as default and can install it with sudo pacman -S shelly. Arch users can pull it from the AUR via yay or paru, or download the standalone x64 tarballs directly from the GitHub releases page. The full changelog, architecture docs, and ABI specifications are all available on the project site.
Shelly currently sits at 968 stars and 81 forks on GitHub. At this pace, expect more stabilization patches later this week. The aarch64 flag and cache management tweaks in 3.0.3 are probably worth your attention first.
Head here to see the full v3.0.3 release notes.
