Bump zwave-js from 14.0.0 to 14.3.7

[dependabot]

Bumps zwave-js from 14.0.0 to 14.3.7.

Release notes

Sourced from zwave-js's releases.

Release v14.3.7

Bugfixes

• Fixed: Firmware updates fail to start on some devices with error "invalid hardware version" (#7452)

Changes under the hood

• Classes that emit events are now based on the DOM compatible EventTarget class instead of Node.js's proprietary EventEmitter. This means that some methods like prependListener no longer exist, but we haven't found any usage of this in the wild.

Release v14.3.6

Bugfixes

• Fixed another issue where some CC API methods would incorrectly fail validation of their arguments, causing the node interview to fail (#7435)

Release v14.3.5

Bugfixes

• Fixed an issue that prevented the nvmedit CI utility from starting (#7432)
• Fixed an issue where some CC API methods would incorrectly fail validation of their arguments (#7433)

Release v14.3.4

Bugfixes

• Fixed an issue where CC classes would have a different name when zwave-js was loaded as CommonJS, changing how those CCs were handled (#7426)

Changes under the hood

• Argument validation of CC APIs no longer uses require calls and explains the validation errors much better (#7407)

Release v14.3.3

Bugfixes

• Fix parsing of some older 500 series NVM formats (#7399)
• Fixed an issue where mock-server would not start due to an incorrect module format (#7401)
• Fixed an issue where the auto-generated argument validation for CC API methods would not work correctly in some cases when zwave-js was bundled (#7403)

Config file changes

• Add HomeSys HomeMech-2001/2 (#7400)

Release v14.3.2

Bugfixes

• Fixed an issue where encoding a buffer as an ASCII string would throw an error on Node.js builds without full ICU (#7395)

Release v14.3.1

Config file changes

• Ignore setpoint range for Ecolink TBZ500 (#7393)

Changes under the hood

• Further reduce dependency on Node.js internals (#7394)

Release v14.3.0

This release is broken. Do not use!

This release adds support for using the WebCrypto API as the cryptography backend. Unlike the node:crypto module, this API is supported by all modern browsers and JS runtimes.

Technically this is a breaking change, as SecurityManager2 now needs to be instantiated asynchronously using await SecurityManager2.create() instead of new SecurityManager2(). However, we don't expect anyone to use this class directly, so this will not be marked as a semver-major release.

... (truncated)

Changelog

Sourced from zwave-js's changelog.

14.3.7 (2024-12-02)

Bugfixes

• Fixed: Firmware updates fail to start on some devices with error "invalid hardware version" (#7452)

Changes under the hood

• Classes that emit events are now based on the DOM compatible EventTarget class instead of Node.js's proprietary EventEmitter. This means that some methods like prependListener no longer exist, but we haven't found any usage of this in the wild.

14.3.6 (2024-11-22)

Bugfixes

• Fixed another issue where some CC API methods would incorrectly fail validation of their arguments, causing the node interview to fail (#7435)

14.3.5 (2024-11-22)

Bugfixes

• Fixed an issue that prevented the nvmedit CI utility from starting (#7432)
• Fixed an issue where some CC API methods would incorrectly fail validation of their arguments (#7433)

14.3.4 (2024-11-20)

Bugfixes

• Fixed an issue where CC classes would have a different name when zwave-js was loaded as CommonJS, changing how those CCs were handled (#7426)

Changes under the hood

• Argument validation of CC APIs no longer uses require calls and explains the validation errors much better (#7407)

14.3.3 (2024-11-14)

Bugfixes

• Fix parsing of some older 500 series NVM formats (#7399)
• Fixed an issue where mock-server would not start due to an incorrect module format (#7401)
• Fixed an issue where the auto-generated argument validation for CC API methods would not work correctly in some cases when zwave-js was bundled (#7403)

Config file changes

• Add HomeSys HomeMech-2001/2 (#7400)

14.3.2 (2024-11-12)

Bugfixes

• Fixed an issue where encoding a buffer as an ASCII string would throw an error on Node.js builds without full ICU (#7395)

14.3.1 (2024-11-12)

Config file changes

• Ignore setpoint range for Ecolink TBZ500 (#7393)

Changes under the hood

• Further reduce dependency on Node.js internals (#7394)

14.3.0 (2024-11-11)

This release adds support for using the WebCrypto API as the cryptography backend. Unlike the node:crypto module, this API is supported by all modern browsers and JS runtimes.

Technically this is a breaking change, as SecurityManager2 now needs to be instantiated asynchronously using await SecurityManager2.create() instead of new SecurityManager2(). However, we don't expect anyone to use this class directly, so this will not be marked as a semver-major release.

Changes under the hood

• Improve portability of the library by supporting the WebCrypto API as cryptography backend (#7386)

... (truncated)

Commits

• 6fe88f9 chore: release v14.3.7
• 782914f chore: update changelog
• 18c5e0a fix: only serialize Firmware Update hardware version if defined (#7452)
• f2d7b3e chore(deps-dev): bump @​microsoft/api-extractor from 7.47.9 to 7.48.0 (#7449)
• f27e9fb chore(deps-dev): bump turbo from 2.2.3 to 2.3.3 (#7446)
• c0c3a17 chore(deps-dev): bump dprint from 0.47.2 to 0.47.5 (#7445)
• cb2d73e docs: remove requirement for error handler (#7438)
• 6a0d95c refactor: use DOM compatible EventTarget to replace Node.js's EventEmitter (#...
• ef8f276 chore: release v14.3.6
• 2ed3466 chore: update changelog
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)