- Documentation update by @Marukome0743 in #1116
- Add workflow file for publishing releases to immutable action package by @Jcambass in #1179
- Update undici from 5.28.2 to 5.28.4 by @dependabot in #1150
- Update actions/checkout from 3 to 4 by @dependabot in #1091
- Update actions/publish-action from 0.2.2 to 0.3.0 by @dependabot in #1147
- Update ts-jest from 29.1.1 to 29.2.5 by @dependabot in #1175
- Update @actions/core from 1.10.1 to 1.11.1 by @dependabot in #1191
- Update @types/jest from 29.5.11 to 29.5.14 by @dependabot in #1193
- Update @actions/cache from 3.2.2 to 4.0.0 by @dependabot in #1194
- Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs.
- Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20.
- Performance optimization that removes unnecessary API calls by @dsame in #1033; fixes #792
- Logs displaying current GitHub API rate limit by @dsame in #1032; addresses #1029
For more information, please read the action documentation and its section about statefulness
In scope of this release we updated actions/core to 1.10.0 for v4 and fixed issues operation count.
- New option labels-to-remove-when-stale enables users to specify list of comma delimited labels that will be removed when the issue or PR becomes stale by @panticmilos #770
- Skip deleting the branch in the upstream of a forked repo by @dsame #913
- abort the build on the error by @dsame in #935
- Allow daysBeforeStale options to be float by @irega in #841
- Use cache in check-dist.yml by @jongwooo in #876
- fix print outputs step in existing workflows by @irega in #859
- Update issue and PR templates, add/delete workflow files by @IvanZosimov in #880
- Update how stale handles exempt items by @johnsudol in #874
Update @actions/core to v1.10.0 (#839)
Issues/PRs default close-issue-reason is now not_planned(#789)
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.