Skip to content

Close stale issues and PRs #550

Close stale issues and PRs

Close stale issues and PRs #550

Triggered via schedule March 31, 2026 02:19
Status Success
Total duration 16s
Artifacts

stale_bot.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
stale
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/stale@5bef64f19d7facfb25b37b414482c7164d639639. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
stale
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
stale
Error delete _state: [403] Resource not accessible by integration
stale
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
stale
No more operations left! Exiting...
stale
Unknown error when unpacking the cache, the process starts from the first issue.
stale
Failed to restore: