Bump actions/stale from 8 to 9

[dependabot]

Bumps actions/stale from 8 to 9.

Release notes

Sourced from actions/stale's releases.

v9.0.0

Breaking Changes

1. Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs.
2. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20.

What Else Changed

1. Performance optimization that removes unnecessary API calls by @​dsame #1033 fixes #792
2. Logs displaying current github API rate limit by @​dsame #1032 addresses #1029

For more information, please read the action documentation and its section about statefulness

New Contributors

• @​jmeridth made their first contribution in actions/stale#984
• @​nikolai-laevskii made their first contribution in actions/stale#1020
• @​dusan-trickovic made their first contribution in actions/stale#1056
• @​aparnajyothi-y made their first contribution in actions/stale#1110

Full Changelog: actions/stale@v8...v9.0.0

Changelog

Sourced from actions/stale's changelog.

Changelog

[7.0.0]

⚠️ Breaking change ⚠️

• Allow daysBeforeStale options to be float by @​irega in actions/stale#841
• Use cache in check-dist.yml by @​jongwooo in actions/stale#876
• fix print outputs step in existing workflows by @​irega in actions/stale#859
• Update issue and PR templates, add/delete workflow files by @​IvanZosimov in actions/stale#880
• Update how stale handles exempt items by @​johnsudol in actions/stale#874

[6.0.1]

Update @​actions/core to v1.10.0 (#839)

[6.0.0]

⚠️ Breaking change ⚠️

Issues/PRs default close-issue-reason is now not_planned(#789)

[5.1.0]

Don't process stale issues right after they're marked stale [Add close-issue-reason option]#764#772 Various dependabot/dependency updates

4.1.0 (2021-07-14)

Features

• Ability to exempt draft PRs

4.0.0 (2021-07-14)

Features

• options: simplify config by removing skip stale message options (#457) (6ec637d), closes #405 #455
• output: print output parameters (#458) (3e6d35b)

Bug Fixes

• dry-run: forbid mutations in dry-run (#500) (f1017f3), closes #499
• logs: coloured logs (#465) (5fbbfba)
• operations: fail fast the current batch to respect the operations limit (#474) (5f6f311), closes #466
• label comparison: make label comparison case insensitive #517, closes #516
• filtering comments by actor could have strange behavior: "stale" comments are now detected based on if the message is the stale message not who made the comment(#519), fixes #441, #509, #518

Breaking Changes

... (truncated)

Commits

• 28ca103 Upgrade Node to v20 (#1110)
• b69b346 build(deps-dev): bump @​types/node from 18.16.18 to 20.5.1 (#1079)
• 88a6f4f build(deps-dev): bump typescript from 5.1.3 to 5.2.2 (#1083)
• 796531a Merge pull request #1080 from akv-platform/fix-delete-cache
• 8986f62 Don not try to delete cache if it does not exists
• cab99b3 fix typo proceeded/processed
• 184e7af Merge pull request #1064 from actions/dependabot/npm_and_yarn/typescript-esli...
• 523885c chore: update eslint-plugin, parser and eslint-plugin-jest
• 2487a1d build(deps-dev): bump @​typescript-eslint/eslint-plugin
• 60c722e Merge pull request #1063 from actions/dependabot/npm_and_yarn/jest-29.6.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ksunden]

Based on those release notes, I think we may wish to bump down the number we process per run...

I'm tempted to suggest going significantly down to start with and ramping back up to approximately the level we have now where ~10 things get flagged per run usually.

Thoughts? In particular, @rcomer I know you have adjusted that number a few times.

[rcomer]

Agreed, since the action will no longer start from the oldest issue and work forward but start from where it finished last time, if we leave the operations limit as it is now we will get far too many new labels on each run. To add a new label, the action uses up four operations. So I suggest we decide the maximum number of new labels we want on a run (five?) and multiply that by 4 to set the operations-per-run.

I think this also means that, once the new labels are added, those issues won't be re-checked until the action has worked through all ~1500 open issues and PRs. That is clearly going to take a long time, so the action won't be removing the label (if someone posts a new comment) or closing issues after a month. I wonder if we could have a second workflow using the same action that only does these cleanup steps. Would that work? Would it be overkill?

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.