Skip to content
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.

[Snyk] Upgrade node-hid from 0.5.4 to 0.7.9 #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade node-hid from 0.5.4 to 0.7.9.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 13 versions ahead of your current version.
  • The recommended version was released 2 years ago, on 2019-05-31.
Release notes
Package name: node-hid
  • 0.7.9 - 2019-05-31

    Linux: Add HID.setDriverType(type) where type can be "libusb" or "hidraw".

    All Linux prebuilds have both driver types.

  • 0.7.8 - 2019-05-01

    Update to support Node v12
    Remove NAN deprecations when building

  • 0.7.7 - 2019-02-15

    Update prebuild and bindings to solve Electron/node-abi prebuild issue #293.

  • 0.7.6 - 2018-12-30

    Works with Electron v4.0.0 and Node v11.x.
    However, prebuilds for Electron v4 had to be removed because prebuild is generating wrong binaries some how.

  • 0.7.5 - 2018-12-30

    Small fixes for Node v11.0 and Electron v4.0.0.

    Note: Removed Electron prebuilds for Node v11 & Electron v4 because still getting the error:

    dyld: lazy symbol binding failed: Symbol not found
     Expected in: flat namespace
    
  • 0.7.4 - 2018-11-24
    No content.
  • 0.7.3 - 2018-07-03

    Update to support Node v10

  • 0.7.2 - 2018-01-09

    In this release:

    • Roll-back HID.setDriverType() support for Linux as it broke prebuilds for everyone (see issue #242)
    • Linux: default to hidraw driver instead of libusb (so usagePage works on Linux, for crypto keys mainly). See details below

    NOTE for Linux users:

    • If you have udev rules they will need to be updated. For instance, for blink(1), the udev rules to support both libusb and hidraw would be in the file /etc/udev/rules.d/51-blink1.rules and contain:
      SUBSYSTEM=="input", GROUP="input", MODE="0666"
      SUBSYSTEM=="usb", ATTRS{idVendor}=="27b8", ATTRS{idProduct}=="01ed", MODE:="666", GROUP="plugdev"
      KERNEL=="hidraw*", ATTRS{idVendor}=="27b8", ATTRS{idProduct}=="01ed", MODE="0666", GROUP="plugdev"
      
      To install the new rules, unplug the HID device and run the command:
      sudo udevadm control --reload-rules
      
  • 0.7.0 - 2018-01-02

    New and potentially breaking changes:

    • Now we can have usagePages on Linux! Should address issues #180 #168 #190
    • Linux hidraw driver is now used by default instead of libusb
    • Linux driver type can be changed at runtime with HID.setDriverType() (see README for details)
    • Both device.write() and device.sendFeatureReport() return number of bytes written. Issue #234

    Note: no prebuilt binaries available for this release

    NOTE for Linux users:

    • Blink1Contro2 uses [email protected] which uses the 'hidraw' driver instead of 'libusb'. This means you need to edit your /etc/udev/rules.d/51-blink1.rules file to also contain:
      KERNEL=="hidraw*", ATTRS{idVendor}=="27b8", ATTRS{idProduct}=="01ed", MODE="0666", GROUP="plugdev"
      
      To install the new rules, unplug the blink(1) device and run the command:
      sudo udevadm control --reload-rules
      
  • 0.6.0 - 2017-12-30
  • 0.5.7 - 2017-08-16
  • 0.5.6 - 2017-08-16
  • 0.5.5 - 2017-08-16
  • 0.5.4 - 2017-01-16
from node-hid GitHub release notes
Commit messages
Package name: node-hid

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Wallet client sets boolean parameters in to True regardless of the input value
1 participant