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)
4.0.0 (2021-07-14)
- options: simplify config by removing skip stale message options (#457) (6ec637d), closes #405 #455
- output: print output parameters (#458) (3e6d35b)
- 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
- 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.