Repository navigation
Fix setup errors and prepare v2.0.11 - #28
Merged
Merged
Conversation
Prepare v2.0.11 with API and real Home Assistant config-flow regressions. Keep polling and entity identities unchanged. Add an explicit, test-gated release-branch workflow. Related to #22.
Use the 2024.8.3 upstream constraints and pre-breaking josepy/pycares majors in the legacy CI environment. This leaves integration runtime dependencies unchanged.
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
1 participant
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.
The setup flow was catching Home Assistant's normal duplicate-entry abort and showing it as an unexpected error. This moves those checks before the API request and checks again before saving an entry.
API errors now carry a specific category instead of being classified by message text. Raw response bodies are no longer included in error messages, and malformed detail responses are rejected before reaching the coordinator. Existing credentials, selections, sensors and polling behaviour stay unchanged.
The new tests exercise the API boundary with real aiohttp and the config-flow helpers with real Home Assistant. CI also runs the existing regression suite. Publishing requires an explicit release/vX.Y.Z branch at the tested main commit; ordinary pushes do not release anything.
Related to #22. This does not claim to fix upstream DNS failures, HTTP 502s or logger disconnections.