Skip to content
No Response

Fix or allow for workaround with classic bug "Plugin execution not covered by lifecycle configuration" #1294

Sign in to view logs

Fix or allow for workaround with classic bug "Plugin execution not covered by lifecycle configuration"

Fix or allow for workaround with classic bug "Plugin execution not covered by lifecycle configuration" #1294

Triggered via issue October 30, 2024 17:38
@SergiuFMSergiuFM
commented on #2828 cc32926
Status Success
Total duration 13s
Artifacts –

no-response.yml

on: issue_comment
noResponse
5s
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/