Sourced from actions/stale's releases.
v6.0.0
:warning: Breaking change :warning:
Issues/PRs default
close-issue-reasonis nownot_planned(#789)V5.2.0
Features: New option
include-only-assignedenables 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/596Fixes: 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
Sourced from actions/stale's changelog.
Changelog
[6.0.0]
:warning: Breaking change :warning:
Issues/PRs default
close-issue-reasonis nownot_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
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-messageandskip-stale-pr-messagewere removed. Instead, setting the optionsstale-issue-messageandstale-pr-messagewill 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 settingskip-stale-issue-messagetotrue.- The
operations-per-runoption 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.
3de2653 Update changelog for v6.0.0 (#829)02e44c8 fix(options)!: Make not_planned the default close-issue-reason (#807)