Skip to content
No Response

Missing a section on bringing VersionTracking migration code together? #2113

Sign in to view logs

Missing a section on bringing VersionTracking migration code together?

Missing a section on bringing VersionTracking migration code together? #2113

Triggered via issue November 7, 2024 11:56
@munkiimunkii
commented on #2487 2f5df77
Status Success
Total duration 10s
Artifacts –

no-response.yml

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