QMK Runs Scheduled Breaking Changes Cycle, Merges Develop into Master

QMK, the Quantum Mechanical Keyboard Firmware that powers thousands of custom keyboards, completed a scheduled breaking-changes cycle and merged the develop branch into master on February 22, 2026. The project describes the cycle as planned and documented, and maintainers run this process roughly quarterly to move accumulated changes from develop into the stable master branch.

The merge on February 22 was explicit: develop was folded into master as part of the breaking-changes window. That label matters because "breaking-changes" indicates upstream adjustments that can alter APIs, keymap behavior, or build configs in ways that are not backward compatible. The project’s cadence of roughly quarterly cycles puts this merge in a predictable rhythm for maintainers and vendors who track QMK updates.

Because QMK powers thousands of custom keyboards, the February 22 merge has downstream effects. Keymap maintainers, keyboard vendors, and builders who pull directly from master will see the merged code in their next builds. If you maintain a keymap or a custom board definition that tracks QMK master, treat the February 22 merge as a trigger to rebase and run a full CI build and on-device test before flashing production units.

Practical steps after this merge are straightforward and concrete. Rebase your local keymap or firmware fork against master as of February 22, 2026, run the project’s build targets for your microcontroller, and test layouts and layers on hardware before pushing new releases. If you rely on continuous integration that tracks master, expect the merged changes to appear in automated builds and local toolchains immediately following the merge.

QMK’s quarterly breaking-changes cycle gives maintainers a clear calendar to plan for potentially disruptive updates. The February 22 merge captures the latest develop work and signals that the next cycle will again consolidate changes roughly three months out. Track develop for in-flight work and treat master after the February 22 merge as the current baseline for production firmware.