New Release v0.9.0 - #39
Merged
Merged
Conversation
added 5 commits
September 6, 2026 09:22
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.
Description
New Release v0.9.0
Motivation and Context
Added
notify.send_messagesupport: Channels using the Home Assistant notify entity architecture (service: notify.send_message+target: notify.<name>) are now dispatched correctly. The target is passed as thetargetkwarg of the service call and thedatakey is no longer injected, both of whichnotify.send_messagerejects.Fixed
['']: A channel with a blanktargetfield no longer overrides the default recipient ofnotify.*services (e.g. SMTP) with an empty list. Empty and whitespace-only entries are now filtered out during target normalization.How has this been tested?
dev container tests and other manual test
Screenshots (if appropriate):
Types of changes
Checklist