QMK Firmware Stays Active With Cleanups, Merges, and Feature Updates

If you've compiled QMK recently or are about to, the short version is this: v0.32.0 landed on February 22, 2026 as the last major breaking change, and commits through late March held firmly to cleanup and CI maintenance. No keymap-breaking surprises are sitting in the current main branch.

That's worth stating plainly because the "QMK is dead" narrative resurfaces in community threads with predictable regularity. The GitHub repository tells a different story. The qmk_firmware main branch registered active merges and formatting commits in the week ending March 29, 2026, and the companion qmk_browser repository received an update as recently as April 1. At 20.2k stars and 43.7k forks, the project's activity metrics don't support the obituary.

The v0.32.0 cycle followed QMK's established breaking-change calendar precisely. The develop branch closed to new merges on February 8, locked entirely for testing on February 15, and shipped the breaking-change merge on February 22. That structured cadence gives board maintainers a predictable window to audit keyboard definitions before anything touches master. Post-v0.32.0, commits shifted to the smaller housekeeping work that keeps the codebase stable across hundreds of supported boards without disturbing the keymap API.

For anyone compiling today, the practical read is straightforward: features like Tap Dance, Mod-Tap, and per-key lighting that function on your current setup should continue to work without changes. Both Atmel AVR and ARM MCU families remain supported, covering most of the custom PCB options currently moving through group buys and in-stock drops.

Maintenance responsibility is distributed across several named stewards rather than sitting on one person. Jack Humbert of OLKB leads core development, ZSA Technology Labs maintains the Ergodox EZ definitions, Zach White covers the Clueboard, and Phil Hagelberg handles the Atreus. That model means board-specific regressions rarely bottleneck on a single contributor and vendor-submitted PRs have a clearer path to merge, which is why vendors shipping QMK-compatible PCBs continue to choose the project over a proprietary firmware stack.

The one discipline worth maintaining before any major version upgrade is checking QMK's breaking-changes history on the docs site. Each quarterly cycle can introduce deprecations or API adjustments that surface only in less common features. The changelog is the authoritative record, and skipping it is how upgrade surprises happen.

The late-March commit activity signals that QMK's maintenance cadence is holding well past v0.32.0. The next breaking-change cycle will follow the same structured calendar, which means the community gets time to prepare rather than scramble.