chore(deps): update actions/stale action to v10

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
actions/stale	action	major	v9 -> v10

---

Release Notes

actions/stale (actions/stale)

v10

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: actions/stale v9 → v10 Update

I've reviewed this dependency update PR. Here's my comprehensive analysis:

Todo List:

• Read the modified workflow file
• Analyze the version change impact
• Check for breaking changes or configuration requirements
• Provide comprehensive review feedback

---

🔍 Code Quality & Best Practices

✅ Good: The change is minimal and focused - only updates the version number from v9 to v10
✅ Good: Workflow configuration remains unchanged, indicating good backward compatibility

🐛 Potential Issues

⚠️ Caution: This is a major version update (v9 → v10) which typically indicates potential breaking changes. However, based on the unchanged configuration, actions/stale v10 appears to maintain backward compatibility with existing parameters.

🚀 Performance Considerations

✅ Neutral: No performance impact expected. The stale action runs on a daily schedule and processes issues/PRs, so any performance improvements in v10 would be beneficial.

🔒 Security Concerns

✅ Good:

• Permissions are appropriately scoped (contents: write, issues: write, pull-requests: write)
• Using pinned major version (@v10) rather than @main is a good security practice
• Action comes from the trusted actions/ organization

Recommendation: Consider pinning to a specific commit SHA for maximum security:

- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5d4a1c3 # v10.0.0

🧪 Test Coverage

ℹ️ Note: This workflow doesn't require traditional testing since it's a scheduled maintenance task. However, you could:

• Monitor the workflow runs after deployment
• Verify it correctly identifies and processes stale issues/PRs
• Test with workflow_dispatch trigger if needed

📋 Configuration Analysis

The workflow uses standard stale action parameters:

• Issues: 30 days to mark stale → 5 days to close (35 days total)
• PRs: 30 days to mark stale → 10 days to close (40 days total)
• Custom messages are configured appropriately

✅ Recommendation

APPROVE: This is a safe dependency update. The actions/stale v10 maintains backward compatibility with the existing configuration, and the change is minimal and well-scoped.

The workflow will continue to function as expected, automatically managing stale issues and pull requests according to your current timeline and messaging configuration.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: actions/stale v9 → v10 Update

Todo List:

• Read the modified workflow file
• Analyze the version change impact
• Check for breaking changes or configuration requirements
• Provide comprehensive review feedback

---

🔍 Code Quality & Best Practices

✅ Good: The change is minimal and focused - only updates the version number from v9 to v10
✅ Good: Workflow configuration remains unchanged, indicating good backward compatibility
✅ Good: Uses semantic versioning with major version pinning (@v10)

🐛 Potential Issues

⚠️ Caution: This is a major version update (v9 → v10) which typically indicates potential breaking changes. However, based on the unchanged configuration, actions/stale v10 appears to maintain backward compatibility with existing parameters.

✅ No Issues Found: All current configuration parameters are standard and well-established in the actions/stale API.

🚀 Performance Considerations

✅ Neutral/Positive: No performance impact expected. The stale action runs on a daily schedule and processes issues/PRs. Any performance improvements in v10 would be beneficial without requiring configuration changes.

🔒 Security Concerns

✅ Good Security Practices:

• Permissions are appropriately scoped (contents: write, issues: write, pull-requests: write)
• Using pinned major version (@v10) rather than @main is good practice
• Action comes from the trusted actions/ organization

Recommendation: Consider pinning to a specific commit SHA for maximum security:

- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5d4a1c3 # v10.0.0

🧪 Test Coverage

ℹ️ Note: This workflow doesn't require traditional testing since it's a scheduled maintenance task. However, you can:

• Monitor workflow runs after deployment
• Verify it correctly identifies and processes stale issues/PRs
• Test manually with workflow_dispatch trigger if needed

📋 Configuration Analysis

The workflow uses standard stale action parameters that are well-supported:

• Timeline: Issues (30+5=35 days), PRs (30+10=40 days)
• Messages: Custom stale and close messages configured appropriately
• Scheduling: Daily cron execution is appropriate for stale management

✅ Overall Recommendation

APPROVE: This is a safe and recommended dependency update. The actions/stale v10 maintains backward compatibility with the existing configuration, and the change is minimal and well-scoped.

Benefits of Update:

• Latest security patches and bug fixes
• Potential performance improvements
• Continued support and maintenance

The workflow will continue to function exactly as expected, automatically managing stale issues and pull requests according to your current timeline and messaging configuration.

---