Skip to content

Validate with hassfest #18

Validate with hassfest

Validate with hassfest #18

Triggered via schedule January 23, 2024 00:42
Status Failure
Total duration 1m 14s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

validate-hacs.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
HACS Action
<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 )
HACS Action
<Integration custom-components/sensor.file_restore> 1/8 checks failed
validate
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
validate
Process completed with exit code 1.
validate
[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.