Skip to content

chore(deps): Bump actions/stale from 9 to 10 #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): Bump actions/stale from 9 to 10 #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/stale.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
- uses: actions/stale@v10
with:
stale-issue-message: 'Marked stale due to inactivity. Will close in 14 days.'
Comment on lines 12 to 15

@llamapreview llamapreview Bot Mar 20, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 | Confidence: High

  • The PR updates actions/stale from v9 to v10. According to the release notes, v10.0.0 contains a breaking change: "Upgrade to node 24 by @salmanmkc in Upgrade to node 24 actions/stale#1279. Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release." This is a public API/behavior change that could break existing workflows. The workflow currently uses runs-on: ubuntu-latest, which should automatically provide compatible runner versions over time, but there could be a transition period where the action fails due to runner version mismatch. This requires explicit verification that the GitHub Actions runner environment meets the minimum version requirement.

  • Speculative: The actions/stale v10 release includes several behavioral changes worth noting: 1) The action is stateful (continues from previous runs when hitting operation limits), which was introduced in v9 but is relevant for scheduling considerations. 2) Version 9 also introduced breaking changes from Node.js 16 to Node.js 20. Since we're moving directly from v9 to v10, we're subject to both sets of breaking changes. The workflow should be tested to ensure the stateful behavior doesn't cause unexpected results with the current schedule (cron: '0 9 * * 1') and operation limits. While the configuration appears standard, the cumulative effect of these breaking changes warrants validation.

  • The update addresses a security vulnerability. The release notes mention: "Upgrade form-data to bring in fix for critical vulnerability by @gowridurgad in Bump form-data to bring in fix for critical vulnerability actions/stale#1277." While this doesn't directly introduce a security issue in our codebase, it mitigates a potential vulnerability in a dependency used by the GitHub Action. This is a positive security improvement that should be highlighted as a benefit of the upgrade.

stale-pr-message: 'Marked stale due to inactivity. Will close in 14 days.'
Expand Down
Loading