ci(stale): let the stale job save its progress between runs

[GeiserX]

The stale workflow can't save its place between runs. actions/stale v11 keeps its progress in an Actions cache named _state. Before saving, it lists the repo's caches and deletes the old _state through the API, and the next run looks it up the same way. Those calls need the actions scope, and the delete needs write. Our permissions block only grants issues and pull-requests, so they fail, and a run that hits operations-per-run starts over from the first issue next time.

This adds actions: write, the first line of the permissions block the actions/stale README recommends.

Summary by CodeRabbit

• Chores
  • Updated permissions for project maintenance automation to support its configured issue and pull-request tasks. This administrative change does not alter the product experience or add, remove, or change any user-facing capabilities. No new features or bug fixes are included in this update.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: GeiserX/Wayback-Diff/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 83980fb0-4348-44d9-91ba-7cb8deaf3d8e

📥 Commits

Reviewing files that changed from the base of the PR and between ec42400 and 8220e4d.

📒 Files selected for processing (1)

• .github/workflows/stale.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The stale workflow now grants actions: write permission. Its existing issue and pull-request write permissions remain unchanged.

Changes

Stale workflow permissions

Layer / File(s)	Summary
Workflow permission update .github/workflows/stale.yml	The workflow adds actions: write and retains its existing issue and pull-request write permissions.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 8220e

The scheduled stale job uses the added permission to preserve progress between runs, with no untrusted event-controlled code executed by the workflow. No actionable merge-blocking risk is established.

Architecture Summary

Architecture risk: 🔵 Low · up to 8220e

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/stale.yml: The workflow permissions now include actions: write; the existing issue and pull-request write permissions are unchanged.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: granting the stale job permission to save progress between runs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}