Skip to content

Bump universal-silabs-flasher to 0.1.2 #156849

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.

Sign up for GitHub

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

Jump to bottom
Merged
zweckj merged 1 commit into from
Nov 19, 2025
Merged

Bump universal-silabs-flasher to 0.1.2 #156849

zweckj merged 1 commit into from
Nov 19, 2025

Conversation

@puddly
Copy link
Contributor

@puddly puddly commented Nov 19, 2025

Proposed change

Bump universal-silabs-flasher to v0.1.2 (this skips v0.1.1).

These two releases fix a bug with OpenThread RCP firmware communication when migrating away from Thread, along with fixing a few edge cases when entering the bootloader when an adapter is configured to use a hardware trigger that is non-functional.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copilot AI review requested due to automatic review settings November 19, 2025 05:49
@puddly puddly requested a review from a team as a code owner November 19, 2025 05:49
@home-assistant
Copy link

home-assistant bot commented Nov 19, 2025

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (homeassistant_hardware) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant_hardware can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign homeassistant_hardware Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

Copilot AI reviewed Nov 19, 2025
View reviewed changes
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the universal-silabs-flasher dependency from version 0.1.0 to 0.1.2 (skipping 0.1.1) to fix bugs related to OpenThread RCP firmware communication during Thread migration and bootloader entry edge cases with non-functional hardware triggers.

Key changes:

  • Bumped universal-silabs-flasher from 0.1.0 to 0.1.2 across all requirement files and the manifest

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
requirements_test_all.txt Updated universal-silabs-flasher version to 0.1.2 for test requirements
requirements_all.txt Updated universal-silabs-flasher version to 0.1.2 for all requirements
homeassistant/components/homeassistant_hardware/manifest.json Updated universal-silabs-flasher version to 0.1.2 in integration manifest

@zweckj zweckj merged commit 938da38 into home-assistant:dev Nov 19, 2025
73 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Nov 20, 2025
@puddly puddly added this to the 2025.11.3 milestone Nov 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

Copilot code review Copilot Copilot left review comments

@zweckj zweckj zweckj approved these changes

Assignees

No one assigned

Labels

bugfix cherry-picked cla-signed integration: homeassistant_hardware Quality Scale: No score small-pr PRs with less than 30 lines.

Projects

None yet

Milestone

2025.11.3

Development

Successfully merging this pull request may close these issues.

3 participants

@puddly @zweckj @frenck