Shelly 2.4.1.2 landed on July 6, 2026, with a focused set of patches for Arch’s package management stack. Shelly isn’t pacman itself, it’s a tool that talks directly to libalpm, the same core library pacman is built on, giving it pacman-equivalent behavior with a different (in Shelly’s case, graphical) frontend on top.

What Got Fixed

The changelog covers four targeted issues rather than a broad feature update. A chroot fix corrects pkexec so it finally passes the correct user through to makepkg, a bug that previously caused permission mismatches when building packages inside a chroot environment. There’s also a child process spawning correction, a version bump to optdeppkg’s dependency resolution logic, and a cleanup for an AUR package handling bug that was silently stripping unresolved version constraints from dependency strings, a subtle bug that could let a package install against a dependency version it wasn’t actually compatible with.

# Anyone building packages inside a chroot benefits directly from the pkexec fix
sudo -u builduser makepkg -s

None of these are the kind of headline features that generate their own release notes elsewhere, but the pkexec and AUR version-constraint fixes both touch correctness issues that could otherwise cause confusing, hard-to-diagnose build or install failures.

Why CachyOS Cares

The more notable part of this release is context rather than the changelog itself: CachyOS has officially adopted Shelly as its default graphical package manager for CachyOS 2604, replacing Octopi. CachyOS is an Arch-based distribution focused on performance-tuned kernels and package builds, and its choice of default tooling tends to get watched closely by the broader Arch-derivative ecosystem, EndeavourOS and Manjaro among them, as a signal of which community tools are gaining traction.

# libalpm-based tools operate on the same package database pacman does
pacman -Qi package-name

Because Shelly and pacman both operate against the same underlying libalpm database and package cache, switching between them, or running both side by side, doesn’t create the kind of conflicting-state problems you’d see mixing package managers built on genuinely different backends.

Should Arch Users Care About This Specifically

If you’re running vanilla Arch with plain pacman and no graphical frontend, this release doesn’t directly affect you unless you already use Shelly. If you’re on CachyOS, or considering it, the Octopi-to-Shelly default switch is the more relevant piece of news: it changes what ships out of the box on a fresh install, not what’s available to install afterward. Existing CachyOS installs that already have Octopi configured won’t be force-migrated; the change applies going forward to new installs and explicit opt-ins.

The Bigger Picture

Arch’s ecosystem has always supported multiple package management frontends against the same libalpm/pacman foundation, pamac, octopi, and now an increasingly capable shelly among them. Point releases like 2.4.1.2 that quietly fix chroot and dependency-resolution correctness bugs are unglamorous but matter more than they might seem, since these are exactly the kind of bugs that surface as “my AUR package won’t build right” reports on forums without an obvious root cause.