Skip to content

Fixing how the brightness attribute gets set. #8

Fixing how the brightness attribute gets set.

Fixing how the brightness attribute gets set. #8

Re-run triggered November 1, 2023 22:11
Status Failure
Total duration 1m 44s
Artifacts

pull.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
Run tests
Process completed with exit code 1.
Validate
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
Validate
Process completed with exit code 1.
Check style formatting
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-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 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/