Skip to content

fix: do not change name entry from config flow #145

fix: do not change name entry from config flow

fix: do not change name entry from config flow #145

Triggered via pull request September 10, 2024 20:24
Status Failure
Total duration 41s
Artifacts

test.yml

on: pull_request
Matrix: Run tests
Validate
32s
Validate
Check style formatting
10s
Check style formatting
coverage
0s
coverage
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Run tests (3.12)
This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v2.2.4`. Learn more: https://github.blog/changelog/2024-02-13-deprecation-notice-v1-and-v2-of-the-artifact-actions/
Check style formatting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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 use a deprecated Node.js version and will be forced to run on node20: actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/