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

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
• Dependency updates

v3.0.18

• Add any-of-labels option
• Add only-issue-labels, only-pr-labels
• Clean up, testing and dependency version bumps

v3.0.17

• Bug fixes, refactoring and milestone exemption