Skip to content
Validate with hassfest

[2024] Modernize development environment (devcontainer, pre-commit etc) #488

Sign in to view logs

[2024] Modernize development environment (devcontainer, pre-commit etc)

[2024] Modernize development environment (devcontainer, pre-commit etc) #488

Triggered via pull request January 7, 2024 17:42
@iMicknliMicknl
synchronize #83
fix/code_standards_2024
Status Failure
Total duration 1m 14s
Artifacts –

hassfest.yml

on: pull_request
validate
1m 5s
validate
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
validate
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
validate
[REQUIREMENTS] Unable to parse package version (=1.1.0) for sagemcom_api.
validate
Process completed with exit code 1.
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/