Skip to content

Validate HACS

Validate HACS #33

Triggered via schedule October 12, 2023 00:10
Status Success
Total duration 1m 38s
Artifacts

hacs-workflow.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
validate-hacs
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
validate-hacs
Process completed with exit code 1.
validate-hacs
<Validation topics> failed: The repository has no valid topics (More info: https://hacs.xyz/docs/publish/include#check-repository )
validate-hacs
<Validation brands> failed: The repository has not been added as a custom domain to the brands repo (More info: https://hacs.xyz/docs/publish/include#check-brands )
validate-hacs
<Validation hacsjson> failed: extra keys not allowed @ data['codeowners'] (More info: https://hacs.xyz/docs/publish/include#check-hacs-manifest )
validate-hacs
<Integration neilzilla/hass-renpho> 3/8 checks failed
validate-hacs
[CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.