Skip to content

Lock Threads

Lock Threads #1251

Triggered via schedule March 11, 2026 05:03
Status Success
Total duration 9s
Artifacts

lock_threads.yml

on: schedule
lock_all_after_1y_of_inactivity
5s
lock_all_after_1y_of_inactivity
lock_invalid_issues
3s
lock_invalid_issues
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
lock_invalid_issues
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dessant/lock-threads@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
lock_all_after_1y_of_inactivity
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dessant/lock-threads@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/