Skip to content

ci: add hassfest and HACS validation - #2

Merged
michaeln31 merged 3 commits into
developfrom
ci/f2-hassfest-hacs
Jul 6, 2026
Merged

ci: add hassfest and HACS validation#2
michaeln31 merged 3 commits into
developfrom
ci/f2-hassfest-hacs

Conversation

@michaeln31

@michaeln31 michaeln31 commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds hassfest and hacs jobs to ci.yml
  • Fixes trivially-addressable gaps upfront: adds integration_type: hub to manifest.json and creates strings.json (mirrors translations/en.json)
  • hassfest runs as continue-on-error: true until requirements in manifest.json are pinned (B5 scope)
  • hacs job runs without continue-on-error — expected to pass clean

Test plan

  • hacs job passes green
  • hassfest job runs (may fail on unpinned requirements — expected, continue-on-error)
  • lint and test jobs still pass

Add hassfest and hacs jobs to ci.yml. Fix trivially-addressable gaps
upfront: add integration_type to manifest.json and create strings.json
matching translations/en.json. Hassfest runs continue-on-error until
requirements are pinned in B5.
Remove invalid icon field from manifest.json (icons go in icons.json).
Fix services.yaml: response key must be {optional: bool}, and target
is required alongside response. Use hacs/action@main (v1.1.0 tag does
not exist).
Sort manifest.json keys in HA-required order (domain, name, then
alphabetical). Remove response/target from services.yaml - response
key format is not yet supported in current hassfest schema. Remove
domains from hacs.json (deprecated key in newer HACS format).
@michaeln31
michaeln31 merged commit f6bf06a into develop Jul 6, 2026
4 checks passed
@michaeln31
michaeln31 deleted the ci/f2-hassfest-hacs branch July 6, 2026 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant