Bump actions/stale from 5 to 6

[dependabot]

Bumps actions/stale from 5 to 6.

Release notes

Sourced from actions/stale's releases.

v6.0.0

⚠️ Breaking change ⚠️

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

V5.2.0

Features: New option include-only-assigned enables users to process only issues/PRs that are already assigned. If there is no assignees and this option is set, issue will not be processed per: issue/596

Fixes: Fix date comparison edge case PR/816

Dependency Updates: PR/812

Fix issue when days-before-close is more than days-before-stale

fixes a bug introduced in #717

fixed in #775

v5.1.0

[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

Changelog

Sourced from actions/stale's changelog.

Changelog

[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

• The options skip-stale-issue-message and skip-stale-pr-message were removed. Instead, setting the options stale-issue-message and stale-pr-message will be enough to let the stale workflow add a comment. If the options are unset, a comment will not be added which was the equivalent of setting skip-stale-issue-message to true.
• The operations-per-run option will be more effective. After migrating, you could face a failed-fast process workflow if you let the default value (30) or set it to a small number. In that case, you will see a warning at the end of the logs (if enabled) indicating that the workflow was stopped sooner to avoid consuming too much API calls. In most cases, you can just increase this limit to make sure to process everything in a single run.

Commits

• 3de2653 Update changelog for v6.0.0 (#829)
• 02e44c8 fix(options)!: Make not_planned the default close-issue-reason (#807)
• See full diff 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 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)

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Upgrading GitHub Stale Action to the Latest Version 🆙

📊 Key Changes

• Updated the actions/stale GitHub action from version 5 to version 6 in the stale workflow file 🔄

🎯 Purpose & Impact

• Purpose: To ensure the repository uses the most recent and improved version of the stale action for better performance and new features 🔧
• Impact: Users can expect more reliable and potentially enhanced stale issue handling within the project's GitHub issues, leading to better project maintenance and community interaction 🔍✨