Liquorix Ships Kernel 7.2-12, With the Real Story Buried in the CI Pipeline
A clean 7.2.7 merge, an ABI flip to 7.x, and an AI-co-authored rebuild of the Arch build pipeline.
Liquorix just added version 7.2-12 to its lineup. Maintainer Steven Barrett pushed today, tagging commit 73bb2ab6ac and signing it with his verified GPG key. On paper it's a routine merge: it pulls upstream Linux 7.2.7 and bumps the Debian ABI from 6-1 to 7-1. The changelog says little.
The entry itself is a two-liner. "merge v7.2.7," then "update version to 7.2.7-1." That's the whole thing, and Barrett signs it off as Steven Barrett steven@liquorix.net. Don't read too much into those two lines, though. The meaningful work in this release is buried in the Arch Linux build pipeline, and three of the six commits touching 7.2-12 list an AI as a co-author.
A clean step onto 7.2.7
For context, 7.2-11 landed September 14. It merged v7.2.6 and conveniently skipped v7.2.5. Eight days later, 7.2-12 arrives as a clean one-step merge of v7.2.7. Either Barrett decided 7.2.5 didn't warrant its own build, or he consolidated the earlier releases and resumed normal cadence as the 7.2 line matures ahead of 7.3-rc work. That's the sensible read.
The ABI name also moved from 6-1 to 7-1, a small but deliberate signal. Combine that with the 7.2/master default branch and the steady march through 7.2.x releases and it's clear the hand-off from the 6.x era is formal at last.
This is one of the most actively maintained enthusiast kernels around. Over the 7.2 line alone there are 12 releases so far; the 7.1 series pulled off 21. At peak in early September, Barrett was shipping near-daily packages during those tuning sprints.
The latest patch set, v7.2.7-lqx1, is the largest of this recent run at roughly 35,925 net lines. It carries Project-C forward, that sustained hardening pass on sched/alt that dominated September's sprint. If you recall the thread: 7.2-5 kept task pairs together in the SMT balance, 7.2-6 reverted that, and 7.2-10 added handling for busy wakers and non-SMT cores. 7.2-12 bundles no new named Project-C heuristic. It's a clean merge with the prior patch set refreshed on top of 7.2.7.
The Arch pipeline, and Claude
Here's where it gets interesting. The compare between 7.2-11 and 7.2-12 shows six commits. Five touch kernel packaging. Three touch Arch Linux CI and build infrastructure. All three of those CI commits carry the trailer: Co-Authored-By: Claude Fable 5.1.
Barrett is using an Anthropic-powered assistant for build engineering. That's about as mainstream an example of AI-augmented kernel packaging as you'll find today. Note that the scheduler patches themselves carry no such co-authorship. That's his own work.
The three CI commits do real homework. First, a new Jenkinsfile (77 lines) replaces a job that used to re-implement the Dockerfile inline. Now the Arch build job builds from the same Dockerfile Barrett uses locally. He added a BASE_IMAGE build arg so CI pulls the base image from a registry mirror instead of Docker Hub, since mirrors.kernel.org times out from EC2. The pacman mirror also moved to mirror.quantum5.ca.
Second, Jenkins now drives builds through make targets. "make bootstrap-arch build-binary-arch means CI runs the exact same path a local build would." GPG keys get imported on the agent and mounted into the container by the existing docker_build-binary.sh helper. He also taught docker_bootstrap-image.sh to pass BASE_IMAGE through from the environment.
Third, he swapped wget for curl. Debian cloud images ship curl but not wget. Leaving a required package out of the CI agents just burned build time.
The most telling detail is that the pipeline refuses to publish unsigned packages. It greps for .sig files before anything reaches origin.liquorix.net. That plugs a real gap. Community issues from #218 (YouTube in Firefox freezing machines) to #226-227 (regression freezes, DKMS build failures) point to a user base that is heavily gaming and desktop-weighted. When freezes and latency spikes are the recurring complaint, package integrity stops being abstract.
On the flip side, this is a lot of plumbing nobody installs directly. It's exactly the kind of behind-the-scenes work that keeps signed packages trustworthy, though. You don't see it until a release breaks.
As usual, Liquorix is installable via the one-line curl-to-bash script:
curl -s 'https://liquorix.net/install-liquorix.sh' | sudo bash
Head here to the GitHub page.
