ci: add hassfest validation job#24
Merged
Merged
Conversation
Adds `home-assistant/actions/hassfest@master` as a required CI job. HACS publishing requires both hacs/action and hassfest to pass. Also adds hassfest to the release job's needs list. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add http to manifest.json dependencies to satisfy hassfest validation for the StaticPathConfig/hass.http usage. Remove async_setup() since its setdefault call is redundant — async_setup_entry handles dict init. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Keys must be: domain, name, then alphabetical order. Co-Authored-By: Claude Sonnet 4.6 <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.
Summary
home-assistant/actions/hassfest@masteras a required CI jobhacs/action(already present) andhassfestto passhassfestto thereleasejob'sneedslist so releases only happen after validationTest plan
hassfestjob appears and passes in GitHub Actions on this PR