Bump to 0.0.19 and add its release notes - #20
Merged
Merged
Conversation
A maintenance release: PR #19 is everything since 0.0.18, and it changed no behaviour. The notes say so plainly rather than dressing internal work up as a feature - there is nothing for a user to do, and every entity keeps its id, its state and its history. What it is worth releasing for is the type gate: the integration is now checked against a real Home Assistant on every push, which is how the four incorrect framework calls in #19 were found. None was reachable at runtime, so the notes do not claim otherwise. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LLPEGFSy3fLEuXNUPAPWR4
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.
Release prep for 0.0.19. Two files:
release_notes/0.0.19.mdand the manifest version.What is in this release
Everything since 0.0.18 is #19, which changed no behaviour. So 0.0.19 is a maintenance release, and the notes say that in the first line rather than dressing internal work up as a feature — no new entities, no renamed ones, no settings to revisit, same minimum of Home Assistant 2024.11, every entity keeping its id, state and history.
What it is worth releasing for is the type gate: the integration is now checked against a real Home Assistant on every push, which is how the four incorrect framework calls in #19 were found. None of those was reachable at runtime, and the notes are careful not to imply otherwise — they were static mistakes of the kind that sit quietly until a Home Assistant release changes something underneath them.
The notes also credit the review bot for catching the first type gate resolving every framework type to
Any, since that is the more useful story for anyone reading them later.Checked before pushing
python -m pytest -q— 359 passedruff check .— clean (0.15.8, as CI pins)manifest.jsonparses and reads0.0.19, which is what the release workflow's manifest check compares againstThe minimum Home Assistant version is unchanged and stays correct: nothing in #19 raised the floor.
SensorEntityDescription,DeviceInfo,DeviceEntryType,EntityCategoryand a genericCoordinatorEntityall predate 2024.11, andhacs.jsonstill declares2024.11.0withtest_integration_hygienepinning it.After merging
Dispatch the Release workflow with version
0.0.19. It tags, re-runs the tests and ruff against the tag, checks the manifest agrees, and publishes usingrelease_notes/0.0.19.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01LLPEGFSy3fLEuXNUPAPWR4
Generated by Claude Code