Sync/upstream main 2026 08 - #82
Closed
antoinevalentinHA wants to merge 10 commits into
Closed
Conversation
- Declare PEP 517/518 build backend (setuptools>=40.8.0, wheel) so source installs (git @main) are reproducible across pip/uv versions. - Remove stdlib modules asyncio/logging from install_requires and requirements.txt (runtime-neutral; avoids pulling abandoned PyPI backports from the same index that can fail to resolve). - Default LIB_VERSION to 0.0.0 to guard against empty-string builds. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Publish a built wheel + sdist as GitHub Release assets when a version tag (v*) is pushed, so a Home Assistant integration installed via HACS can pin its manifest requirements to a stable release asset URL instead of a moving branch. Remove the PyPI publish workflow, which cannot run on this fork. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bw61z1ycazvGosRw13Emg4
…tion-wv3759 Add tag-triggered release workflow with wheel asset for HACS
Add a workflow_dispatch trigger (with a version input) to the release workflow so a release can be produced without pushing a tag directly: the workflow creates the tag at the checked-out commit and attaches the built wheel + sdist to the GitHub Release. Useful in environments where tag pushes are restricted. Claude-Session: https://claude.ai/code/session_01Bw61z1ycazvGosRw13Emg4 Co-authored-by: Claude <noreply@anthropic.com>
Declare >= floors (no upper caps) for the runtime dependencies so that Home Assistant's uv-based install can be satisfied by packages already provided by HA core instead of querying the HA wheels index (wheels.home-assistant.io) for the latest compatible version of each unpinned dependency. That index querying is what breaks integration installs when the index has an incident (observed HTTP 522). Floors for the HA-core-shared packages (bleak, bleak-retry-connector, async-timeout, cryptography) match the versions HA core 2026.6.0 ships, so they are satisfied by the already-installed packages without a download. No upper bound is set, to avoid conflicting with a newer version HA may have installed. crcmod and pyasn1 are not HA core deps and get a modest floor only. This reduces exposure to wheels-index outages but does not eliminate it: a full index outage can still make uv fail. It is a robustness measure, not a fix for the outage itself. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bw61z1ycazvGosRw13Emg4
…tion-wv3759 Add lower-bound version floors to runtime dependencies
Brings in upstream's fragment buffering for encrypted BLE notifications (8905896), which supersedes the local workaround that silently dropped frames failing to decrypt: fragments are now reassembled instead of lost. Conflict in device_reader.py resolved on the upstream base, keeping only the fork's BleakError handling on the two handshake write_gatt_char calls. This restores the MessageType.CHALLENGE_ACCEPTED branch, which the fork had dropped in 6984197 -- without it, challenge-accepted frames fell through to the AES path and raised the very "Data not aligned on aes block size" error the workaround was suppressing. Also picks up EP760/PR100V2/EL32V2 device support and bluetti-scan improvements. Fork-specific release tooling (release.yml, pyproject.toml, dependency floors, LIB_VERSION fallback) is unaffected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Drives _notification_handler with a well-formed CHALLENGE frame against a client whose write_gatt_char always raises BleakError. Fails with `bleak.exc.BleakError: Not connected` escaping the handler before the fix, passes after. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.