Skip to content

service weirdness?

service weirdness? #91

Triggered via issue November 25, 2024 13:31
Status Success
Total duration 14s
Artifacts

tags.yml

on: issues
close-read-the-field-manual
0s
close-read-the-field-manual
comment-unreleased-fix
0s
comment-unreleased-fix
close-unsupported-device
0s
close-unsupported-device
close-unsupported-os
0s
close-unsupported-os
close-unsupported-configuration
0s
close-unsupported-configuration
comment-upstream
0s
comment-upstream
comment-need-more-info-to-fix
3s
comment-need-more-info-to-fix
close-invalid
0s
close-invalid
comment-out-of-scope
0s
comment-out-of-scope
close-wontfix
0s
close-wontfix
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
comment-need-more-info-to-fix
The following actions uses node12 which is deprecated and will be forced to run on node16: peter-evans/create-or-update-comment@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
comment-need-more-info-to-fix
The following actions use a deprecated Node.js version and will be forced to run on node20: peter-evans/create-or-update-comment@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
comment-need-more-info-to-fix
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/