No Response

No Response #1

Sign in to view logs

Triggered via schedule September 21, 2024 01:07

sergiotarxz

dev

Status Success

Total duration 13s

Artifacts –

no-response.yml

on: schedule

waiting-for-answer

needs-user-action

Annotations

6 warnings

waiting-for-answer

The following actions uses node12 which is deprecated and will be forced to run on node16: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

waiting-for-answer

The following actions use a deprecated Node.js version and will be forced to run on node20: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

needs-user-action

The following actions uses node12 which is deprecated and will be forced to run on node16: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

needs-user-action

The following actions use a deprecated Node.js version and will be forced to run on node20: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cant-reproduce

The following actions uses node12 which is deprecated and will be forced to run on node16: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

cant-reproduce

The following actions use a deprecated Node.js version and will be forced to run on node20: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/