search

home-assistant / addons

:heavy_plus_sign: Docker add-ons for Home Assistant
https://home-assistant.io/hassio/
Apache License 2.0
1.57k stars 1.52k forks source link

Bump zwavejs to 13.10.3 #3819

Closed MindFreeze closed 2 weeks ago

MindFreeze commented 2 weeks ago

And zwavejs server to 1.39.0

Summary by CodeRabbit

coderabbitai[bot] commented 2 weeks ago
📝 Walkthrough
📝 Walkthrough ## Walkthrough The changes in this pull request involve updates to the configuration files for the `zwave_js` project. The `build.yaml` file has modified version numbers for `ZWAVEJS_SERVER_VERSION` and `ZWAVEJS_VERSION`. The `config.yaml` file has been updated to a new version number and includes additional configuration options, specifically `network_key`, `emulate_hardware`, and `disable_controller_recovery`, enhancing its flexibility while maintaining backward compatibility. The `CHANGELOG.md` file has been updated to reflect the new version and includes sections for new features, bug fixes, and configuration changes. ## Changes | File | Change Summary | |--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| | zwave_js/build.yaml | - Updated `ZWAVEJS_SERVER_VERSION` from `1.38.0` to `1.39.0`
- Updated `ZWAVEJS_VERSION` from `13.9.0` to `13.10.3` | | zwave_js/config.yaml | - Updated version from `0.8.1` to `0.9.0`
- Added new key `network_key: match(|[0-9a-fA-F]{32,32})?`
- Added new key `emulate_hardware: bool?`
- Added new key `disable_controller_recovery: bool?` | | zwave_js/CHANGELOG.md | - Added new version entry `## 0.9.0`
- Added new features section
- Added new bug fixes section
- Added new configuration file changes section
- Added new detailed changelogs section | ## Sequence Diagram(s) ```mermaid sequenceDiagram participant User participant ZWaveJS_Config participant ZWaveJS_Build User->>ZWaveJS_Config: Update configuration ZWaveJS_Config-->>User: Configuration updated (version 0.9.0) ZWaveJS_Config->>ZWaveJS_Build: Update version parameters ZWaveJS_Build-->>ZWaveJS_Config: Build configuration updated (versions updated) ```
📜 Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
📥 Commits Reviewing files that changed from the base of the PR and between a8d0438a9d258ce2835d775d84c36a3089a8763e and 97d78c9e4e0ed8ff049a4be9caebcccbb294c7fe.
📒 Files selected for processing (1) * `zwave_js/CHANGELOG.md` (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
zwave_js/CHANGELOG.md (6) Pattern `*/**(html|markdown|md)`: - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted. - Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness. - In step-by-step instructions, front the location phrase in the instructional sentence. - In step-by-step instructions, front the 'goal' in the instructional sentence. - In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence. - do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner' --- Pattern `*/**(html|markdown|md)`: - Use bold to mark UI strings. - If "" are used to mark UI strings, replace them by bold. --- Pattern `*/**(html|markdown|md)`: - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if" --- Pattern `*/**(html|markdown|md)`: - Use sentence-style capitalization also in headings. --- Pattern `*/**(html|markdown|md)`: do not comment on HTML used for icons --- Pattern `*/**(html|markdown|md)`: Avoid flagging inline HTML for embedding videos in future reviews for this repository.
🪛 LanguageTool
zwave_js/CHANGELOG.md [style] ~13-~13: Consider using a different verb for a more formal wording. Context: ...nValue ### Bug fixes - Z-Wave JS: Fixed an issue where preferred scales were no... (FIX_RESOLVE)
🔇 Additional comments (4)
zwave_js/CHANGELOG.md (4) `7-9`: **Features section is clear and well-structured.** The features are clearly described and provide good context about the new capabilities added to both Z-Wave JS and Z-Wave JS Server. --- `13-16`: **Bug fixes are well documented with clear impact descriptions.** Each bug fix entry clearly describes what was fixed and provides good context about the issue that was resolved.
🧰 Tools
🪛 LanguageTool [style] ~13-~13: Consider using a different verb for a more formal wording. Context: ...nValue ### Bug fixes - Z-Wave JS: Fixed an issue where preferred scales were no... (FIX_RESOLVE)
--- `20-29`: **Config file changes are well organized and descriptive.** The changes to device configurations are clearly listed with specific model numbers and parameter details, making it easy for users to identify relevant changes for their devices. --- `33-38`: **Skip previously addressed link issues.** The link ordering and server link issues have already been addressed in previous reviews.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` or `@coderabbitai title` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.