Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 17, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
actions/stale action major v3.0.19 -> v6.0.1

Release Notes

actions/stale

v6.0.1

Compare Source

Update @​actions/core to 1.10.0 #​839

Full Changelog: actions/stale@v6.0.0...v6.0.1

v6.0.0

Compare Source

⚠️ Breaking change ⚠️

Issues/PRs default close-issue-reason is now not_planned(#​789)

v5.2.0

Compare Source

Features:
New option include-only-assigned enables 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/596

Fixes:
Fix date comparison edge case PR/816

Dependency Updates:
PR/812

v5.1.1: Fix issue when days-before-close is more than days-before-stale

Compare Source

fixes a bug introduced in #​717

fixed in #​775

v5.1.1: Fix issue when days-before-close is more than days-before-stale

Compare Source

fixes a bug introduced in #​717

fixed in #​775

v5.1.0

Compare Source

[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

v5.0.0

Compare Source

Features

v4.1.0

Compare Source

Features

v4.0.0

Compare Source

⚠️ This version contains breaking changes ⚠️

Features
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.

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

kodiakhq[bot]
kodiakhq bot previously approved these changes Oct 17, 2022
lukasholzer
lukasholzer previously approved these changes Dec 14, 2022
@renovate renovate bot dismissed stale reviews from lukasholzer and kodiakhq[bot] via b328597 December 16, 2022 14:05
@renovate renovate bot force-pushed the renovate/actions-stale-6.x branch from 02bc8b8 to b328597 Compare December 16, 2022 14:05
@kodiakhq kodiakhq bot merged commit 4883383 into main Dec 16, 2022
@kodiakhq kodiakhq bot deleted the renovate/actions-stale-6.x branch December 16, 2022 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants