Mark inactive issues and pull requests #25350
stale.yml
on: schedule
mark-inactive-30d
17s
mark-inactive-90d
28s
Annotations
8 warnings
mark-inactive-30d
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/stale@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
mark-inactive-30d
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/stale@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
mark-inactive-30d
No more operations left! Exiting...
|
mark-inactive-30d
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 50
|
mark-inactive-90d
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/stale@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
mark-inactive-90d
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/stale@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
mark-inactive-90d
No more operations left! Exiting...
|
mark-inactive-90d
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 50
|