docs: add service icon banner to README #95
martinargalasvalidate.yml
on: push
validate-hacs
37s
hassfest
18s
Annotations
3 errors and 3 warnings
|
hassfest
Process completed with exit code 1.
|
|
hassfest
[TRANSLATIONS] Invalid translations/en.json: extra keys not allowed @ data['config']['step']['plex']['selector']. Got {'skip_plex': {'options': {'setup': 'Set up Plex', 'skip': 'Skip Plex'}}}
|
|
hassfest
[TRANSLATIONS] Invalid strings.json: extra keys not allowed @ data['config']['step']['plex']['selector']. Got {'skip_plex': {'options': {'setup': 'Set up Plex', 'skip': 'Skip Plex'}}}
|
|
hassfest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hassfest
[CONFIG_FLOW] Config flows that are discoverable need to set a unique ID
|
|
hassfest
[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.
|