Skip to content

HACS validate

HACS validate #2533

Triggered via schedule October 14, 2024 00:42
Status Failure
Total duration 44s
Artifacts

hacs-validate.yml

on: schedule
Hassfest validation
13s
Hassfest validation
HACS validation
34s
HACS validation
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 3 warnings
Hassfest validation
[SERVICES] Service reload has no name and is not in the translations file
Hassfest validation
[SERVICES] Service installed has no name and is not in the translations file
Hassfest validation
[TRANSLATIONS] Invalid translations/en.json: required key not provided @ data['services']['installed']['name']. Got None
Hassfest validation
Process completed with exit code 1.
Hassfest validation
[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.
Hassfest validation
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
HACS validation
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/