javascript
javascript copied to clipboard
Bump actions/stale from 5.2.0 to 6.0.1
Bumps actions/stale from 5.2.0 to 6.0.1.
Release notes
Sourced from actions/stale's releases.
v6.0.1
Update
@actions/core
to 1.10.0 #839Full Changelog: https://github.com/actions/stale/compare/v6.0.0...v6.0.1
v6.0.0
:warning: Breaking change :warning:
Issues/PRs default
close-issue-reason
is nownot_planned
(#789)
Changelog
Sourced from actions/stale's changelog.
[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 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-message
andskip-stale-pr-message
were removed. Instead, setting the optionsstale-issue-message
andstale-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 settingskip-stale-issue-message
totrue
.- 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.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)