Repository navigation
fix: client and gateway pin blaueis-core exactly - #15
Merged
Merged
Conversation
Home Assistant installs each requirement on its own with pip --upgrade. A container rebuild after 0.1.0rc2 was published let blaueis-client 0.1.0rc1's blaueis-core~=0.1.0rc1 range lift core to rc2 under an integration pinned to rc1, which broke its setup. The packages are released together, so the client and the gateway now depend on exactly their own core version; a test keeps versions and pins in lockstep. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
blaueis-clientandblaueis-gatewaynow depend on exactly theblaueis-coreversion they are released with (==0.1.0rc2today, instead of~=0.1.0rc1/~=0.1.0rc2).Why — an outage on the maintainer's install on 2026-10-18: Home Assistant installs each
requirements:entry on its own withuv pip install --upgrade, in manifest order. After a Core update rebuilt the container, the integration still pinnedblaueis-core==0.1.0rc1andblaueis-client==0.1.0rc1; installing the client with--upgradelet itsblaueis-core~=0.1.0rc1range lift core to the newly published0.1.0rc2, which no longer has a private name that build imported. The entry stayed insetup_erroruntil the matching integration build was installed. Reproduced locally on Python 3.14 with the same install sequence.packages/blaueis-{client,gateway}/pyproject.toml:blaueis-core==0.1.0rc2.packages/blaueis-core/tests/test_lockstep.py: the three versions are equal and the client and gateway pin core to exactly that version (fails on the old~=form, checked).docs/releasing.mdstep 1 explains the exact pin; the 0.1.0 CHANGELOG notes it.Takes effect with the next library tag. The integration side already guards against private imports since
tests/unit/test_library_surface.py(ha-midea PR #45).🤖 Generated with Claude Code