Skip to content
No Response

Improved the way pings are done to the remote control / dev server #27

Sign in to view logs

Improved the way pings are done to the remote control / dev server

Improved the way pings are done to the remote control / dev server #27

Triggered via issue November 4, 2024 21:09
@unodevopsunodevops
commented on #18687 94b1943
Status Success
Total duration 13s
Artifacts –

no-response.yml

on: issue_comment
noResponse
4s
noResponse
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
noResponse
The following actions uses node12 which is deprecated and will be forced to run on node16: lee-dohm/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
noResponse
The following actions use a deprecated Node.js version and will be forced to run on node20: lee-dohm/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/