Close/Lock issues after inactivity

Close/Lock issues after inactivity #1405

Sign in to view logs

Triggered via schedule November 3, 2024 02:12

facebook-github-bot

main

Status Success

Total duration 10s

Artifacts –

needs-reply.yml

on: schedule

close-issues-needs-more-info

lock-issues-after-closed

Annotations

5 warnings

lock-issues-after-closed

The following actions uses node12 which is deprecated and will be forced to run on node16: dessant/lock-threads@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

lock-issues-after-closed

The following actions use a deprecated Node.js version and will be forced to run on node20: dessant/lock-threads@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

lock-issues-after-closed

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/

close-issues-needs-more-info

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

close-issues-needs-more-info

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