latest-debs

Why latest-debs?

Debian freezes package versions for years. latest-debs tracks popular developer tools and publishes each new upstream release as a properly packaged .deb — automatically, within hours of release. One apt upgrade and everything is current.

Install

On Debian, via extrepo:

sudo extrepo enable latest-debs
sudo apt update
sudo apt install <package>

Swap <package> for any tool in the live package list below — e.g. sudo apt install uv eza lazygit.

Or manually:

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://raw.githubusercontent.com/latest-debs/apt-repo/main/latest-debs.asc | sudo gpg --dearmor --yes -o /etc/apt/keyrings/latest-debs.gpg
echo "deb [signed-by=/etc/apt/keyrings/latest-debs.gpg] https://latest-debs.github.io/apt-repo/ $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/latest-debs.list
sudo apt update

Packages ↻ Refresh now

Loading the tool registry…

How it works

Every package in latest-debs is built by debian-multiarch-builder, a reusable GitHub Action that turns an upstream GitHub release into a proper multi-architecture .deb — no manual packaging step, no per-tool build scripts to maintain. Each <tool>-debian repo in this org is just a thin package.yaml pointing the action at an upstream project; the action handles architecture detection, cross-building, and Debian control-file generation from there.

That's also why a new tool can go from "requested" to "packaged" in a single PR: adding latest-debs support for something new is mostly writing a package.yaml, not writing a build. See the project itself if you want to package your own tool for Debian, upstream release or not.

Supported

Dates per debian.org/releases. Bookworm's regular security support window has closed; it's now community-maintained under LTS until mid-2028. Trixie's end dates aren't officially set yet — the "projected" values follow Debian's typical ~3-year security / ~5-year LTS cadence (per endoflife.date/debian) and will move once Debian publishes the real ones.

Architectures

Only architectures at least one tracked tool actually publishes a Linux build for are listed. Device-count/popularity are qualitative context, not precise figures — there's no live metric for that; "Available suites" is live, pulled from each suite's own Release file.