chore(deps): pin @openmouse/protocol to the wired button-mapping driver - #115
Draft
Pochiiko wants to merge 1 commit into
Draft
chore(deps): pin @openmouse/protocol to the wired button-mapping driver#115Pochiiko wants to merge 1 commit into
Pochiiko wants to merge 1 commit into
Conversation
DO NOT MERGE AS-IS. This pins 06997e4, the head of mouse-protocol OpenMouse-Project#26, which is not on that repo's main yet. Regenerate against main's tip once OpenMouse-Project#26 merges, then take this out of draft. Draft so the integration is reviewable alongside OpenMouse-Project#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. OpenMouse-Project#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.
Pochiiko
force-pushed
the
chore/protocol-pin-wired-buttons
branch
from
August 17, 2026 05:09
4b06614 to
b505b55
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Blocked on OpenMouse-Project/mouse-protocol#26 — don't merge this until that one is merged.
That PR confirms class 0x02 button mapping over the Viper V3 Pro's cable. openmouse builds against an exact protocol commit, so the Buttons tab stays hidden over the cable until this pin moves.
Currently pinned to 35ccb8c, the head of #26, which isn't on main yet. Once #26 merges the pin needs regenerating against main's tip.
Lockfile only — no source change, since availability.ts never looks at the transport. npm run check: 81/81.