Skip to content

⬆️ Updates actions/stale action to v10#545

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/actions-stale-10.x
Open

⬆️ Updates actions/stale action to v10#545
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/actions-stale-10.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 7, 2025

This PR contains the following updates:

Package Type Update Change
actions/stale action major v3v10

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

actions/stale (actions/stale)

v10.2.0

Compare Source

v10.1.1

Compare Source

What's Changed

Bug Fix
Improvement
Dependency Upgrades

New Contributors

Full Changelog: actions/stale@v10...v10.1.1

v10.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/stale@v10...v10.1.0

v10.0.0

Compare Source

What's Changed

Breaking Changes
Enhancement
Dependency Upgrades
Documentation changes

New Contributors

Full Changelog: actions/stale@v9...v10.0.0

v10

Compare Source

v9.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/stale@v9...v9.1.0

v9.0.0

Compare Source

Breaking Changes

  1. 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.
  2. 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.

What Else Changed

  1. Performance optimization that removes unnecessary API calls by @​dsame #​1033 fixes #​792
  2. Logs displaying current github API rate limit by @​dsame #​1032 addresses #​1029

For more information, please read the action documentation and its section about statefulness

New Contributors

Full Changelog: actions/stale@v8...v9.0.0

v9

Compare Source

v8

Compare Source

v8.0.0

Compare Source

⚠️ This version contains breaking changes ⚠️

What's Changed

  • 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

Breaking Changes

  • In this release we prevent scenarios when the build is not interrupted on some exceptions, which led to successful builds when they are supposed to fail

Example

name: 'Remove labels when the issue or PR becomes stale'
on:
  schedule:
    - cron: '30 1 * * *'

permissions:
    pull-requests: write

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v8
        with:
          labels-to-remove-when-stale: 'label1,label2'

v7

Compare Source

v7.0.0

Compare Source

⚠️ This version contains breaking changes ⚠️

What's Changed

Breaking Changes

  • In this release we prevent this action from managing the stale label on items included in exempt-issue-labels and exempt-pr-labels
  • We decided that this is outside of the scope of this action, and to be left up to the maintainer

New Contributors

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

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)

v6

Compare Source

v5.2.1: Update @​actions/core for v5

Compare Source

In scope of this release we updated actions/core to 1.10.0 for v5: #​958

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

v5

Compare Source

v4.1.1

Compare Source

In scope of this release we updated actions/core to 1.10.0 for v4 and fixed issues operation count.

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.

v4

Compare Source

v3.0.19

Compare Source

  • Enhance logs to provide more detailed output
  • Split certain options to be more granular for Pull Requests vs Issues:
    • any-of-issue-labels
    • any-of-pr-labels
    • remove-issue-stale-when-updated
    • remove-pr-stale-when-updated
  • Dependency updates

v3.0.18

Compare Source

  • Add any-of-labels option
  • Add only-issue-labels, only-pr-labels
  • Clean up, testing and dependency version bumps

v3.0.17

Compare Source

  • Bug fixes, refactoring and milestone exemption

v3.0.16

Compare Source

  • Minor bugfixes and logging improvements

v3.0.15

Compare Source

  • Add milestone exemption
  • Add start date filtering
  • Add conditional days before close to different types of issues
  • Better logging and updated dependencies

v3.0.14

Compare Source

  • Update label handling to account for localization
  • Update dependencies

v3.0.13

Compare Source

  • Don't print untrusted info to STDOUT.

v3.0.12

Compare Source

  • Update distribution to latest packages

v3.0.11

Compare Source

  • Update dependencies
  • Add a close issue label

v3.0.10

Compare Source

Update licenses in action

v3.0.9

Compare Source

v3.0.8

Compare Source

  • Add an option for a close message on stale

v3.0.7

Compare Source

  • Add a way to sort issues when querying for staleness

v3.0.6

Compare Source

  • Fix an issue with issue closure based on stale timing
  • Add promise error handling to github API calls

v3.0.5

Compare Source

  • Update stale -> close transition behavior

v3.0.4

Compare Source

  • Fix bad un-staling logic for stale issues
  • Add better logging even when not in debug mode
  • Fix operation counts

v3.0.3

Compare Source

  • Fix an issue where the bot thought its own comments should un-stale an issue

v3.0.2

Compare Source

  • Fix issue with close days behavior that become more noticeable on auto-issue close.

v3.0.1

Compare Source

Bugfix for older stale label support (fixed failure).


Configuration

📅 Schedule: (in timezone Europe/Moscow)

  • Branch creation
    • "after 10pm every weekday,before 5am every weekday,every weekend"
  • 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 was generated by Mend Renovate. View the repository job log.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Sep 7, 2025

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Sep 7, 2025

🏷️ [bumpr]
Next version:v2.0.2
Changes:v2.0.1...AlexRogalskiy:renovate/actions-stale-10.x

1 similar comment
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Sep 7, 2025

🏷️ [bumpr]
Next version:v2.0.2
Changes:v2.0.1...AlexRogalskiy:renovate/actions-stale-10.x

@renovate renovate Bot force-pushed the renovate/actions-stale-10.x branch from a4a6e43 to 2455516 Compare April 19, 2026 10:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants