RPM 6.1.0 is officially out as the first stable release under a new kernel-inspired cadence, promising predictable biannual updates instead of the unpredictable 4.x era. The update restores NSS-based user and group lookups that broke years ago, slaps installation times down by roughly 26 percent on Linux 5.11 and glibc 2.34, and adds literal macro modifiers alongside PKCS#11 token signing.

RPM 6.1.0 Ships: The First Release Under Linux RPM's New, Kernel-Inspired Cadence

RPM 6.1.0 is officially out. If you've been waiting for the package manager to stop breaking your build environments, you're in luck. The release lands on August 20, 2026, delivering restored NSS lookups, a claimed 26 percent install-time reduction on modern kernels, and the first full implementation of its newly adopted release model.

RPM has anchored Red Hat, Fedora, SUSE, openSUSE, and a dozen other distributions since its first version control commit in 1995. For over two decades, its versioning was, frankly, a guessing game. The 4.x series rolled major breakage into what were supposed to be minor updates, which left packagers and sysadmins scrambling. That era is now firmly behind it.

A Cadence Borrowed from the Kernel

In the months since the project announced its new release policy, the 6.x series has followed a strict rhythm. Under this framework, the major version locks the on-disk package format. The minor digit covers features and bugfixes, released biannually or quarterly, with only release candidates leading up to it. Micro releases are strictly security patches. The developers openly admitted that the old model was painful for both users and the development team, and they made it a point to strip major breakage out of feature releases.

The 6.1.0 timeline followed that exactly. An alpha dropped in April 2025, followed by betas through late 2025, stable 6.0.0 in September, a couple of patch releases, and now the feature-focused 6.1.0. No more year-long alpha cycles. No more surprises in what should be a minor bump.

Getting there took a deliberate pace. The last 4.x releases were described by the team as rough patches applied over foundational changes, but the new cadence promises predictability instead. You can check your local RPM version against this schedule if you've been tracking the RC train, because the gap between candidates and stable is now measured in weeks, not seasons.

What Actually Changed in 6.1.0

The biggest headline for working users is the restoration of NSS-based user and group lookups. That feature was quietly disabled in 4.19.0, which broke a workflow that enterprise deployments have relied on for years. It's back by default in 6.1.0, and you can still opt out if your setup actually needs it. The keystore now uses a separate lock from the transaction lock, too, which means you can finally run parallel queries against the database without everything grinding to a halt.

Install performance gets a meaningful lift on Linux 5.11 and glibc 2.34 or newer through more efficient file descriptor handling. Systems performing bulk installations or live OS updates will see the difference most. Not cheap to measure, but the regression is real. If you're stuck on older kernels, you'll still get the NSS fix and the macro improvements, but don't expect a faster dnf run.

Macro authors finally get literal and one-shot modifiers via a new <l> and <o> syntax, giving you precise control over when expansion happens. rpmbuild now spills the build environment to rpmbuild.env, which is a quiet lifesaver for debugging CI pipelines. The signing toolchain gained PKCS#11 token support, so HSM and smart card workflows just got a lot easier. And after years of compiler friction, the project now builds cleanly with Clang, which matters to distros that mandate it.

What's Next and Where to Grab It

The roadmap points to 6.2 in Q3 or Q4 of this year. Symbol versioning for librpm is the immediate target, followed by early work on durable transactions and database parking for image reproducibility. The 2027 horizon includes filesystem capability checks, copy-on-write payload installation, and true multiarch support. It's a lot of ground covered, and the pace looks sustainable.

Head here to download the new release.