Bump zwave-js from 14.0.0 to 14.3.4

[dependabot]

Bumps zwave-js from 14.0.0 to 14.3.4.

Release notes

Sourced from zwave-js's releases.

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.

Changes under the hood

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

Release v14.2.0

Changes under the hood

• Improved tree-shakability (#7376, #7379)
• CCs are now parsed and serialized asynchronously, Message instances are serialized asynchronously (#7377)

Release v14.1.0

Features

• Allow specifying RF region for OTA firmware updates if the region is unknown or cannot be queried (#7369)
• Add tryUnzipFirmwareFile utility to support zipped OTA firmware files (#7372)

Bugfixes

• Parse negative setback state consistently (#7366)
• Ignore LR nodes when computing neighbor discovery timeout (#7367)

... (truncated)

Changelog

Sourced from zwave-js's changelog.

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)

14.2.0 (2024-11-07)

Changes under the hood

• Improved tree-shakability (#7376, #7379)
• CCs are now parsed and serialized asynchronously, Message instances are serialized asynchronously (#7377)

14.1.0 (2024-11-06)

Features

• Allow specifying RF region for OTA firmware updates if the region is unknown or cannot be queried (#7369)
• Add tryUnzipFirmwareFile utility to support zipped OTA firmware files (#7372)

Bugfixes

• Parse negative setback state consistently (#7366)
• Ignore LR nodes when computing neighbor discovery timeout (#7367)
• Automatically fall back to Europe when setting region to Default (EU) (#7368)

... (truncated)

Commits

• b42dec2 chore: release v14.3.4
• 0c9560f chore: update changelog
• 2cffecf fix: ensure CC classes are not randomly renamed during CJS transform (#7426)
• ef68078 feat: use static imports in @validateArgs(), elaborate errors (#7407)
• 5e6a537 chore(deps): bump cross-spawn from 7.0.3 to 7.0.6 (#7421)
• 80528ed chore(deps): bump @​eslint/plugin-kit from 0.2.0 to 0.2.3 (#7406)
• cecd3b7 chore: release v14.3.3
• 5d539fc chore: update changelog
• fe29afb fix: use static predicate if class instanceof check fails in validateArgs...
• b7b2a82 fix: mock-server would not start due to ESM/CJS confusion (#7401)
• 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)

[dependabot]

Superseded by #1353.