Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2025

This PR contains the following updates:

Package Type Update Change
actions/stale action major v7.0.0 -> v10.0.0

Release Notes

actions/stale (actions/stale)

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

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

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'

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@renovate renovate bot requested a review from drupol as a code owner September 4, 2025 04:06
Copy link

what-the-diff bot commented Sep 4, 2025

PR Summary

  • Updated GitHub Action Version for Pruning
    The version of the GitHub Action we use to automatically manage and clean-up old issues and pull requests has been updated. This enhancement from actions/stale@v7.0.0 to actions/stale@v10.0.0 makes sure we're using the latest technology, which could help to increase efficiency and accuracy when dealing with stale items.

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