Skip to content

Check device type before setting an potentially unsupported model (#139) #177

Check device type before setting an potentially unsupported model (#139)

Check device type before setting an potentially unsupported model (#139) #177

Triggered via push August 27, 2024 15:24
Status Success
Total duration 1m 18s
Artifacts

validate.yaml

on: push
With hassfest
1m 8s
With hassfest
With HACS action
23s
With HACS action
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
With HACS action
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/
With HACS action
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
With hassfest
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/
With hassfest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/