universal-silabs-flasher: Bump flasher and firmwares

[puddly]

https://github.com/NabuCasa/silabs-firmware-builder/releases/tag/v2024.10.21 https://github.com/NabuCasa/universal-silabs-flasher/releases/tag/v0.0.23

Summary by CodeRabbit

• New Features

  • Updated firmware support to EmberZNet version 7.4.4 and universal-silabs-flasher version 0.0.23.
  • Enhanced script for firmware selection and error handling, ensuring better compatibility and reliability with various devices.

• Bug Fixes

  • Improved error handling for firmware download failures.

• Documentation

  • Changelog updated to reflect the new version entries and firmware updates.

[coderabbitai[bot]]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The changes in this pull request include updates to the CHANGELOG.md, build.yaml, and config.yaml files for the silabs_flasher project, reflecting a new version 0.3.1. The changelog details updates to the EmberZNet firmware and the universal-silabs-flasher version. The build.yaml file has updated the UNIVERSAL_SILABS_FLASHER version, and the config.yaml file reflects a version increment. Additionally, the universal-silabs-flasher-up script has been modified to update firmware filenames, enhance device selection logic, and improve error handling.

Changes

File Path	Change Summary
silabs_flasher/CHANGELOG.md	Added version entry 0.3.1; updated EmberZNet to 7.4.4 and universal-silabs-flasher to 0.0.25.
silabs_flasher/build.yaml	Updated UNIVERSAL_SILABS_FLASHER version from 0.0.22 to 0.0.25.
silabs_flasher/config.yaml	Updated version from 0.3.0 to 0.3.1.
silabs_flasher/rootfs/etc/s6-overlay/scripts/universal-silabs-flasher-up	Updated firmware filenames to 7.4.4.0; enhanced device selection logic; improved error handling.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Script
    participant FirmwareRepo

    User->>Script: Initiate firmware flashing
    Script->>Script: Check device type
    alt USB device with valid info
        Script->>FirmwareRepo: Fetch firmware for device
        FirmwareRepo-->>Script: Return firmware file
        Script->>Script: Flash firmware
        Script-->>User: Flashing successful
    else Invalid device
        Script-->>User: Log warning and exit
    end

---

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 5417a283bbf54e05c03cb1268e58aff6ba75c815 and eb21acd97499fb8a15237ff42fb9667e5403b2ac.

📒 Files selected for processing (2)

• silabs_flasher/CHANGELOG.md (1 hunks)
• silabs_flasher/build.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• silabs_flasher/CHANGELOG.md
• silabs_flasher/build.yaml

---

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>, 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 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.