matter_server: Bump Python Matter server to 6.2.1

[agners]

Bump Python Matter Server to 6.2.1

This adds a new configuration option enable_test_net_dcl which enables PAA root certificates and other device information from test-net DCL.

Summary by CodeRabbit

• New Features

  • Expanded logging capabilities with new log_level_sdk option.
  • Introduced beta option to install the latest beta version on startup.
  • Added enable_test_net_dcl option to use test-net DCL for development and testing.

• Chores

  • Bumped version of Python Matter Server to 6.2.1.
  • Updated image versions for aarch64 and amd64 architectures in build configuration.

[coderabbitai]

Walkthrough

Walkthrough

The latest update introduces version 6.2.1 of the Python Matter Server, incorporating enhanced logging features and new testing configurations. Additionally, the update configures the Matter Server to support test-net DCL for development and testing. This includes changes to configuration files and build scripts to facilitate these new capabilities without altering the declarations of exported or public entities.

Changes

File Path	Change Summary
matter_server/CHANGELOG.md	Updated changelog to introduce version 6.2.1 of the Matter Server
matter_server/DOCS.md	Added new configuration options including log_level_sdk, beta, and enable_test_net_dcl
matter_server/build.yaml	Updated image versions for python-matter-server to 6.2.1
matter_server/config.yaml	Updated version to 6.2.1 and added enable_test_net_dcl option
matter_server/rootfs/.../matter-server/run	Introduced conditional addition of --enable-test-net-dcl to extra_args
matter_server/translations/en.yaml	Added enable_test_net_dcl configuration option with name and description fields

Tip

AI model upgrade

gpt-4o model for reviews and chat is now live

OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our Discord Community to provide any feedback or to report any issues.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 080dbc7 and f9d58a2.

Files selected for processing (6)

• matter_server/CHANGELOG.md (1 hunks)
• matter_server/DOCS.md (1 hunks)
• matter_server/build.yaml (1 hunks)
• matter_server/config.yaml (2 hunks)
• matter_server/rootfs/etc/s6-overlay/s6-rc.d/matter-server/run (1 hunks)
• matter_server/translations/en.yaml (1 hunks)

Additional context used

Path-based instructions (4)

matter_server/build.yaml (4)

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.

matter_server/config.yaml (4)

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.

matter_server/DOCS.md (4)

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.

matter_server/CHANGELOG.md (4)

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.

LanguageTool

matter_server/DOCS.md

[misspelling] ~34-~34: Possible spelling mistake found.
Context: ... component. | | log_level_sdk | Logging level for Matter SDK lo...

(MORFOLOGIK_RULE_EN_US)

---

[misspelling] ~36-~36: Possible spelling mistake found.
Context: ...on on startup | | enable_test_net_dcl | Enable test-net DCL for PAA root cert...

(MORFOLOGIK_RULE_EN_US)

Additional comments not posted (7)

matter_server/build.yaml (1)

3-4: Update image versions for python-matter-server to 6.2.1.

These changes ensure that the python-matter-server is updated to version 6.2.1 for both aarch64 and amd64 architectures. This is consistent with the PR summary.

matter_server/translations/en.yaml (1)

14-18: Add new configuration option enable_test_net_dcl.

The new configuration option enable_test_net_dcl has been added with appropriate name and description fields. This aligns with the PR summary and enhances configurability.

matter_server/config.yaml (3)

2-2: Update version to 6.2.1.

The version has been updated to 6.2.1, which is consistent with the PR summary.

---

27-27: Add enable_test_net_dcl option under options.

The enable_test_net_dcl option has been added under options, defaulting to false. This enhances configurability.

---

32-32: Add enable_test_net_dcl option to schema.

The enable_test_net_dcl option has been added to the schema section, ensuring it is recognized as a valid configuration option.

matter_server/rootfs/etc/s6-overlay/s6-rc.d/matter-server/run (1)

33-35: Add conditional logic for enable_test_net_dcl.

The conditional logic to append --enable-test-net-dcl to extra_args if enable_test_net_dcl is true is correctly implemented. This aligns with the PR summary and enhances functionality.

matter_server/CHANGELOG.md (1)

3-6: Changelog entry for version 6.2.1 is consistent and well-formed.

The changelog entry follows the same format as previous entries and includes a link to the release notes.

---

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
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

[MartinHjelmare]

What's with the version jump? Are we trying to stay with the server version? I don't think we should do that. We should just follow semantic versioning and remain logical. This add-on is separate from the server.