Stale issue and PR workflow #1412
stale.yml
on: schedule
Mark stale issues and PRs
20s
Annotations
6 warnings
|
Mark stale issues and PRs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
|
|
Mark stale issues and PRs
Error delete _state: [403] Resource not accessible by integration - https://docs.github.com/rest/actions/cache#delete-github-actions-caches-for-a-repository-using-a-cache-key
|
|
Mark stale issues and PRs
If you think that not enough issues were processed you could try to increase the quantity related to the operations-per-run (https://github.com/actions/stale#operations-per-run) option which is currently set to 30
|
|
Mark stale issues and PRs
No more operations left! Exiting...
|
|
Mark stale issues and PRs
Unknown error when unpacking the cache, the process starts from the first issue.
|
|
Mark stale issues and PRs
Failed to restore:
|