From b505b55e1501e33871d56b99b83c23bb3d4f5c22 Mon Sep 17 00:00:00 2001 From: Pochiiko Date: Mon, 17 Aug 2026 15:09:09 +1000 Subject: [PATCH] chore(deps): pin @openmouse/protocol to the wired button-mapping driver DO NOT MERGE AS-IS. This pins 06997e4, the head of mouse-protocol #26, which is not on that repo's main yet. Regenerate against main's tip once #26 merges, then take this out of draft. Draft so the integration is reviewable alongside #26. Class 0x02 button mapping is confirmed over the Viper V3 Pro's cable (0x00c0) in that PR; openmouse builds against an exact protocol commit, so the Buttons tab stays hidden over the cable until this pin moves. Rebased onto dev after mouse-protocol main moved to 4f56cdc and dev's pin followed it. #26 was rebased onto that same main first, so 06997e4 contains the Fantech driver as well as the wired flag. Pinning the previous head would have reverted Fantech -- a dependency downgrade wearing the costume of a merge conflict. No source change is needed or made. availability.ts computes razerButtons from status.razerButtonMappings and never looks at the transport. npm run check: 83/83, tsc clean, against this pin. --- package-lock.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package-lock.json b/package-lock.json index b353c6f..cc0bd4c 100644 --- a/package-lock.json +++ b/package-lock.json @@ -460,7 +460,7 @@ }, "node_modules/@openmouse/protocol": { "version": "0.1.0", - "resolved": "git+ssh://git@github.com/OpenMouse-Project/mouse-protocol.git#4f56cdce5b201c08fca93e033577fc5ff1695e68", + "resolved": "git+ssh://git@github.com/OpenMouse-Project/mouse-protocol.git#06997e461dadea0ca45d2894fcc7ebd825ad017c", "engines": { "node": ">=20" }