Sourced from actions/stale's releases.

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

v5.0.0

Features

• Update Runtime to node16

v4.1.0

Features

• Ability to exempt draft PRs

v4.0.0

⚠️ This version contains breaking changes ⚠️

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.

v3.0.19

• Enhance logs to provide more detailed output
• Split certain options to be more granular for Pull Requests vs Issues:
  • any-of-issue-labels
  • any-of-pr-labels
  • remove-issue-stale-when-updated
  • remove-pr-stale-when-updated

... (truncated)

Sourced from actions/stale's changelog.

[5.1.1]

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

[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.

• 9c1b1c6 Changelog 5.1.1
• 2b58cc9 Fix issue when days-before-close is more than days-before-stale (#775)
• 532554b update Changelog
• aaab997 fix(options): add missing close-issue-reason option (#772)
• 136efb5 docs: update example with new version of stale (#765)
• 06d2a39 Add close-issue-reason option (#764)
• 29e800e Remove stale when updated without comment (#717)
• 6b7f971 build(deps): bump github/codeql-action from 1 to 2 (#760)
• 6c298b1 Update CONTRIBUTING.md
• c048b97 Update CONTRIBUTING.md
• Additional commits viewable in compare view

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)