CHANGELOG.md

Changelog

[7.0.0]

:warning: Breaking change :warning:

• Allow daysBeforeStale options to be float by @irega in https://github.com/actions/stale/pull/841
• Use cache in check-dist.yml by @jongwooo in https://github.com/actions/stale/pull/876
• fix print outputs step in existing workflows by @irega in https://github.com/actions/stale/pull/859
• Update issue and PR templates, add/delete workflow files by @IvanZosimov in https://github.com/actions/stale/pull/880
• Update how stale handles exempt items by @johnsudol in https://github.com/actions/stale/pull/874

[6.0.1]

Update @actions/core to v1.10.0 (#839)

[6.0.0]

:warning: Breaking change :warning:

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.