Skip to content

Validate with hassfest #1075

Validate with hassfest

Validate with hassfest #1075

Triggered via schedule September 13, 2023 00:33
Status Failure
Total duration 1m 16s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

hassfest.yaml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
validate
[SERVICES] Service sequence has no name and is not in the translations file
validate
[SERVICES] Service delay has no name and is not in the translations file
validate
[SERVICES] Service popup has no name and is not in the translations file
validate
[SERVICES] Service more_info has no name and is not in the translations file
validate
[SERVICES] Service close_popup has no name and is not in the translations file
validate
[SERVICES] Service notification has no name and is not in the translations file
validate
[SERVICES] Service navigate has no name and is not in the translations file
validate
[SERVICES] Service refresh has no name and is not in the translations file
validate
[SERVICES] Service set_theme has no name and is not in the translations file
validate
[SERVICES] Service console has no name and is not in the translations file
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.
validate
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/