import { _ as _export_sfc, c as createElementBlock, o as openBlock, a8 as createStaticVNode } from "./chunks/framework.B9AX-CPi.js"; const __pageData = JSON.parse('{"title":"QMK Breaking Changes - 2024 November 24 Changelog","description":"","frontmatter":{},"headers":[],"relativePath":"ChangeLog/20241124.md","filePath":"ChangeLog/20241124.md","lastUpdated":null}'); const _sfc_main = { name: "ChangeLog/20241124.md" }; const _hoisted_1 = /* @__PURE__ */ createStaticVNode('
November 2024 brings a relatively lightweight QMK release. As with previous cycles, almost all PRs were related to cleanup or re-organization of aspects of QMK.
One notable item is the removal of arm_atsam
-- this affects users with massdrop/ctrl
or massdrop/alt
keyboards. These have no current replacement, but support for an alternative to the arm_atsam
backend is nearing completion. Unfortunately the alternative backend didn't make this quarter's list of merges, so there's a temporary removal of these boards. Users who need to build for these targets should stay on the 0.26.x
version of QMK until these boards have been restored.
One note with updated keyboard names -- historical keyboard names are still considered valid when using External Userspace for builds. If you're already using External Userspace, you do not need to move your keymap inside your repository.
Old Keyboard Name | New Keyboard Name |
---|---|
saevus/cor | concreteflowers/cor |
saevus/cor_tkl | concreteflowers/cor_tkl |
In line with the notice period, deprecation notices for larger items are listed here.
RGB keycodes have been reworked to allow for both rgblight and rgb_matrix to coexist for the handful of boards in the repo with both enabled. Previously, RGB_xxx
style keycodes were available, but now for rgblight we have UG_xxx
(underglow), and RM_xxx
for rgb_matrix. Default keymaps have been updated to reflect whichever system the respective board enables.
Longer-term, RGB_xxx
style keycodes will be removed, but for now they act as if they're UG_xxx
, and UG_xxx
keycodes act upon both rgblight and rgb_matrix simultaneously. Put simply, the existing RGB_xxx
keycodes act as they always have, giving users time to transition across to the new keycodes instead.
Following on from the last Breaking Changes cycle, Binary blobs for optical sensors have been removed from the QMK codebase. Hooks allowing users to supply their own have been put in place; users wishing to source firmware blobs and integrate them into their keymap may do so. Doing so renders their firmware un-distributable due to licensing incompatibility with the GPL -- as such user firmware containing such blobs must not be distributed.
Please get in touch with the QMK team on Discord if your sensor is no longer functional.
Core:
keymap.json
=> keymap.c
without requiring layers/layout etc. (#23451)get_hardware_id()
to be used for serial number. (#24053)usb_device_state
: consolidate usb state handling across implementations (#24258)k_rgb_matrix_split
(#24388)STM32_PWM_USE_ADVANCED
references (#24432)RING_BUFFERED_6KRO_REPORT_ENABLE
due to disuse. (#24433)qmk find
: expand operator support (#24468)CLI:
qmk new-keyboard
: separate dev board and MCU selection (#24548)Submodule updates:
arm_atsam
platform (#24337)Keyboards:
60_tsangan_hhkb
community layout (#24355)multilayer_rgb
keymap (#24480)Keyboard fixes:
keymap_config.no_gui
within led_update_kb
(#24473)GU_TOGG
keycode (#24474)Others:
data/constants/keycodes
(#24528)Bugs:
', 31); const _hoisted_32 = [ _hoisted_1 ]; function _sfc_render(_ctx, _cache, $props, $setup, $data, $options) { return openBlock(), createElementBlock("div", null, _hoisted_32); } const _20241124 = /* @__PURE__ */ _export_sfc(_sfc_main, [["render", _sfc_render]]); export { __pageData, _20241124 as default };