Restore v0.1.9 Home Assistant discovery compatibility - #7
Merged
Conversation
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.
Summary
v0.1.9-beta32-entity Home Assistant discovery contract as the defaultv0_1_9_standardprofile.all(171 normally, 205 with Grottincludeall=True; generic is 32/36).Version boundary
v0.1.10-betaalready exists as an immutable prerelease, so this corrective line is prepared asv0.1.11-beta. This draft is for testing only.v0.1.9-betaremains the Latest supported release andv0.1.10-betaremains a prerelease.Local evidence
509 passed171 -> 32 -> 205 -> 32Release boundary
Do not merge, tag, publish images, dispatch the release workflow, or update live Home Assistant from this draft. Hosted CI and controlled Home Assistant UAT, including zero new Grott unit/statistics entries in Repairs and verified rollback evidence, must pass first.
Refs #6