Bluetooth-Devices/bleak-esphome - CodSpeed

Bluetooth-Devices

bleak-esphome

Blog Docs Changelog

Performance History

Latest Results

chore(ci): bump the github-actions group across 1 directory with 5 updates Bumps the github-actions group with 5 updates in the / directory: | Package | From | To | | --- | --- | --- | | [actions/setup-python](https://github.com/actions/setup-python) | `6` | `7` | | [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) | `8.2.0` | `10.0.1` | | [CodSpeedHQ/action](https://github.com/codspeedhq/action) | `4` | `5` | | [python-semantic-release/python-semantic-release](https://github.com/python-semantic-release/python-semantic-release) | `10.5.3` | `10.6.2` | | [browniebroke/hacktoberfest-labeler-action](https://github.com/browniebroke/hacktoberfest-labeler-action) | `2.6.0` | `2.7.0` | Updates `actions/setup-python` from 6 to 7 - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](https://github.com/actions/setup-python/compare/v6...v7) Updates `astral-sh/setup-uv` from 8.2.0 to 10.0.1 - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](https://github.com/astral-sh/setup-uv/compare/v8.2.0...v10.0.1) Updates `CodSpeedHQ/action` from 4 to 5 - [Release notes](https://github.com/codspeedhq/action/releases) - [Changelog](https://github.com/CodSpeedHQ/action/blob/main/CHANGELOG.md) - [Commits](https://github.com/codspeedhq/action/compare/v4...v5) Updates `python-semantic-release/python-semantic-release` from 10.5.3 to 10.6.2 - [Release notes](https://github.com/python-semantic-release/python-semantic-release/releases) - [Changelog](https://github.com/python-semantic-release/python-semantic-release/blob/master/CHANGELOG.rst) - [Commits](https://github.com/python-semantic-release/python-semantic-release/compare/v10.5.3...v10.6.2) Updates `browniebroke/hacktoberfest-labeler-action` from 2.6.0 to 2.7.0 - [Release notes](https://github.com/browniebroke/hacktoberfest-labeler-action/releases) - [Changelog](https://github.com/browniebroke/hacktoberfest-labeler-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/browniebroke/hacktoberfest-labeler-action/compare/v2.6.0...v2.7.0) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: astral-sh/setup-uv dependency-version: 10.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: CodSpeedHQ/action dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: python-semantic-release/python-semantic-release dependency-version: 10.6.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions - dependency-name: browniebroke/hacktoberfest-labeler-action dependency-version: 2.7.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot/github_actions/github-actions-47c9d752ac

4 days ago

chore(pre-commit.ci): pre-commit autoupdate updates: - [github.com/astral-sh/ruff-pre-commit: v0.16.4 → v0.16.5](https://github.com/astral-sh/ruff-pre-commit/compare/v0.16.4...v0.16.5)

pre-commit-ci-update-config

5 days ago

feat: warn when a proxy never answers a connect request (#421) Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

main

6 days ago

test: pin the streak reset in async_set_unavailable Removing the reset left all 244 tests green: the existing async_set_unavailable tests execute the line, so line and branch coverage stay at 100% either way and neither can catch its removal. This reset is what re-arms the leading-edge warning after the proxy restart the troubleshooting page recommends, so a later refactor dropping it would slip the next warning from attempt 5 to attempt 60, silently and only in the field. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

philbert:feat/warn-when-proxy-never-answers-connect

7 days ago

test: pin the streak reset in async_set_unavailable Removing the reset left all 244 tests green: the existing async_set_unavailable tests execute the line, so line and branch coverage stay at 100% either way and neither can catch its removal. This reset is what re-arms the leading-edge warning after the proxy restart the troubleshooting page recommends, so a later refactor dropping it would slip the next warning from attempt 5 to attempt 60, silently and only in the field. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

philbert:feat/warn-when-proxy-never-answers-connect

9 days ago

chore(pre-commit.ci): pre-commit autoupdate updates: - [github.com/commitizen-tools/commitizen: v4.17.1 → v4.18.0](https://github.com/commitizen-tools/commitizen/compare/v4.17.1...v4.18.0) - [github.com/astral-sh/ruff-pre-commit: v0.16.3 → v0.16.4](https://github.com/astral-sh/ruff-pre-commit/compare/v0.16.3...v0.16.4)

pre-commit-ci-update-config

12 days ago

docs: note the streak reset in the async_set_unavailable docstring The docstring enumerates this method's effects and this one was left to an inline comment, while docs/api.md autodocs the method as the entry point consumers reach through client_data.bluetooth_device. A consumer reading the rendered reference to decide when to call it would see every other side effect but the one that governs whether the new warning re-arms on its leading edge after a reconnect. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

philbert:feat/warn-when-proxy-never-answers-connect

16 days ago

fix: clear streaks on a dead session and name the repeat unit Streaks survived async_set_unavailable, so after the proxy restart the warning recommends, the leading-edge arm could not fire again for those addresses and the next warning waited on the repeat arm instead. Clear them with the rest of the dead session's state: they describe a session that no longer exists. Cover the streak reset on an error response, which only the success path pinned, so moving that call below the error return can no longer pass. Rename CONNECT_TIMEOUT_WARN_INTERVAL, which read as seconds beside the float-seconds timeouts above it, and say 2026.8.0 "or later" since it has no stable release yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

philbert:feat/warn-when-proxy-never-answers-connect

17 days ago

Latest Branches

N/A

chore(ci): bump the github-actions group across 1 directory with 5 updates#433

4 days ago

18a92cb

dependabot/github_actions/github-actions-47c9d752ac

0%

chore(pre-commit.ci): pre-commit autoupdate#432

5 days ago

7b8b381

pre-commit-ci-update-config

+1%

feat: warn when a proxy never answers a connect request#421

9 days ago

85436fd

philbert:feat/warn-when-proxy-never-answers-connect

© 2026 CodSpeed Technology

Home Terms Privacy Docs