Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump @zwave-js/core from 10.16.0 to 11.13.1 #192

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 1, 2023

Bumps @zwave-js/core from 10.16.0 to 11.13.1.

Release notes

Sourced from @​zwave-js/core's releases.

Release v11.13.1

Bugfixes

  • Fixed a regression from v11.13.0 where Meter CC and Multilevel Sensor CC reports from an endpoint were discarded, although the endpoint did support them, but the root endpoint didn't (#6222)
  • Fixed a startup crash that happens when the controller returns an empty list of nodes (#6220)
  • Fixed an issue where API calls would be rejected early or incorrectly resolved while the driver was still retrying a command to an unresponsive node (#6219)
  • Fixed an issue where the controller would be considered jammed if it responds with a Fail status, even after transmitting (#6211)

Changes under the hood

  • Switched formatting from Prettier to the much faster Dprint (#6198)
  • Added a precommit hook to format files (#6205)
  • Fix type definitions in the documentation for the "firmware update finished" controller event (#6206)
  • Fixed an issue during documentation generation where referencing the same type definition multiple times would not work (#6207)
  • Moved the documentation for Driver.interviewNode to Node.interview (#6209)

Release v11.13.0

Features

  • Auto-detected serialports now prominently include /dev/serial/by-id/* paths (#6182)

Bugfixes

  • Discard Meter CC and Multilevel Sensor CC reports when the node they supposedly come from does not support them (#6178)
  • Abort inclusion when a node with the same ID is already part of the network (#6180)
  • Fixed an issue where a node that does not support S0 and/or S2 was shown with an unknown security class (#6187)
  • Fixed a regression from v11.12.0 where devices with a proprietary field in the device config would not finish the interview (#6202)

Config file changes

  • Remove unnecessary endpoint functionality for CT100 (#6185)

Changes under the hood

  • Extended documentation for parsing QR codes (#6181)
  • Fixed an issue where directly editing driver.options in tests would modify the defaultOptions and influence future driver instances (#6188)

Release v11.12.0

Features

  • When the controller cannot transmit due to being jammed, this is now detected and exposed to applications. In this situation, nodes are no longer being marked as dead. (#6174)
  • A hash of the device config used during the interview is now stored and can be used to detect whether a node needs to be re-interviewed after a configuration update (#6170)

Bugfixes

  • Fixed an issue where 700 series controllers were not soft-reset after NVM backup when soft-reset was disabled via config (#6176)

Config file changes

  • Correct reporting frequency parameter values for Sensative AB Strips Comfort / Drips Multisensor (#6171)

Changes under the hood

  • Config file checks now detect invalid firmware version ranges where min > max (#6169)

Release v11.11.0

Features

  • The driver configuration now includes settings for RF region and TX power which will automatically be configured on startup (#6159)
  • Add support for persistent node-specific defaults for transition duration and volume (#6162)

... (truncated)

Changelog

Sourced from @​zwave-js/core's changelog.

11.13.1 (2023-08-28)

Bugfixes

  • Fixed a regression from v11.13.0 where Meter CC and Multilevel Sensor CC reports from an endpoint were discarded, although the endpoint did support them, but the root endpoint didn't (#6222)
  • Fixed a startup crash that happens when the controller returns an empty list of nodes (#6220)
  • Fixed an issue where API calls would be rejected early or incorrectly resolved while the driver was still retrying a command to an unresponsive node (#6219)
  • Fixed an issue where the controller would be considered jammed if it responds with a Fail status, even after transmitting (#6211)

Changes under the hood

  • Switched formatting from Prettier to the much faster Dprint (#6198)
  • Added a precommit hook to format files (#6205)
  • Fix type definitions in the documentation for the "firmware update finished" controller event (#6206)
  • Fixed an issue during documentation generation where referencing the same type definition multiple times would not work (#6207)
  • Moved the documentation for Driver.interviewNode to Node.interview (#6209)

11.13.0 (2023-08-22)

Features

  • Auto-detected serialports now prominently include /dev/serial/by-id/* paths (#6182)

Bugfixes

  • Discard Meter CC and Multilevel Sensor CC reports when the node they supposedly come from does not support them (#6178)
  • Abort inclusion when a node with the same ID is already part of the network (#6180)
  • Fixed an issue where a node that does not support S0 and/or S2 was shown with an unknown security class (#6187)
  • Fixed a regression from v11.12.0 where devices with a proprietary field in the device config would not finish the interview (#6202)

Config file changes

  • Remove unnecessary endpoint functionality for CT100 (#6185)

Changes under the hood

  • Extended documentation for parsing QR codes (#6181)
  • Fixed an issue where directly editing driver.options in tests would modify the defaultOptions and influence future driver instances (#6188)

11.12.0 (2023-08-16)

Features

  • When the controller cannot transmit due to being jammed, this is now detected and exposed to applications. In this situation, nodes are no longer being marked as dead. (#6174)
  • A hash of the device config used during the interview is now stored and can be used to detect whether a node needs to be re-interviewed after a configuration update (#6170)

Bugfixes

  • Fixed an issue where 700 series controllers were not soft-reset after NVM backup when soft-reset was disabled via config (#6176)

Config file changes

  • Correct reporting frequency parameter values for Sensative AB Strips Comfort / Drips Multisensor (#6171)

Changes under the hood

  • Config file checks now detect invalid firmware version ranges where min > max (#6169)

11.11.0 (2023-08-15)

Features

  • The driver configuration now includes settings for RF region and TX power which will automatically be configured on startup (#6159)
  • Add support for persistent node-specific defaults for transition duration and volume (#6162)

... (truncated)

Commits
  • edb59d8 chore: release v11.13.1
  • be676a8 chore: update changelog
  • c9a4d8a test: fix some TypeScript errors in test files (#6221)
  • d36d791 fix: consider CCs supported by the sending endpoint before discarding unsuppo...
  • fd5eb0e fix: create node instance for controller when node list is empty (#6220)
  • d16e888 fix: don't abort transaction while still retrying (#6219)
  • e8ebb4d chore: add precommit hook to format files (#6205)
  • 1faa09c fix: only consider controller as jammed on status Fail with 0 TX ticks (#6211)
  • fa4ffb5 fix(docs): move Driver.interviewNode to Node.interview (#6209)
  • 6159966 fix(docs): indentation in generated sidebar
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [@zwave-js/core](https://github.com/AlCalzone/node-zwave-js) from 10.16.0 to 11.13.1.
- [Release notes](https://github.com/AlCalzone/node-zwave-js/releases)
- [Changelog](https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md)
- [Commits](zwave-js/node-zwave-js@v10.16.0...v11.13.1)

---
updated-dependencies:
- dependency-name: "@zwave-js/core"
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 1, 2023
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 1, 2023

Superseded by #193.

@dependabot dependabot bot closed this Oct 1, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/zwave-js/core-11.13.1 branch October 1, 2023 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant