Skip to content

Fix stale bot cache issue by adding actions:write permission#3902

Merged
tpantelis merged 2 commits intosubmariner-io:develfrom
tpantelis:fix-stale-bot-cache-issue
Feb 18, 2026
Merged

Fix stale bot cache issue by adding actions:write permission#3902
tpantelis merged 2 commits intosubmariner-io:develfrom
tpantelis:fix-stale-bot-cache-issue

Conversation

@tpantelis
Copy link
Copy Markdown
Contributor

@tpantelis tpantelis commented Feb 18, 2026

Summary

This PR fixes a caching issue in the stale workflow where issues are being perpetually skipped with the message "skipped due being processed during the previous run".

Problem

The stale workflow was lacking the actions:write permission needed to delete/update the cache between runs. Without this permission:

  • The stale action creates a cache of processed issues
  • It cannot delete or update this cache in subsequent runs (403 error)
  • Issues get stuck in a "perpetually processing" state

Solution

Add actions:write to the job permissions in .github/workflows/stale.yml.

References

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflow configuration permissions.

The stale workflow was experiencing a caching issue where issues were
being perpetually skipped with the message "skipped due being processed
during the previous run". This was caused by the workflow lacking the
actions:write permission needed to delete/update the cache between runs.

Without this permission, the stale action creates a cache of processed
issues but cannot delete or update it in subsequent runs, resulting in
a 403 error and issues getting stuck in a "perpetually processing" state.

This fix adds the actions:write permission as recommended in:
actions/stale#1131

Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
@submariner-bot
Copy link
Copy Markdown
Contributor

🤖 Created branch: z_pr3902/tpantelis/fix-stale-bot-cache-issue
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 18, 2026

No actionable comments were generated in the recent review. 🎉


Walkthrough

A GitHub Actions workflow permission was modified to grant write access to the actions permission in .github/workflows/stale.yml. This is a configuration-level change with no functional logic modifications.

Changes

Cohort / File(s) Summary
GitHub Actions Configuration
.github/workflows/stale.yml
Added write permission for actions to the workflow permissions configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding the actions:write permission to fix the stale bot cache issue.
Actionable Comments Resolved ✅ Passed PR contains no unresolved actionable comments. The modification to .github/workflows/stale.yml is complete and focused, adding only the actions: write permission required to fix the stale bot cache issue.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@tpantelis tpantelis enabled auto-merge (rebase) February 18, 2026 02:42
@submariner-bot submariner-bot added the ready-to-test When a PR is ready for full E2E testing label Feb 18, 2026
@tpantelis tpantelis merged commit 11d2997 into submariner-io:devel Feb 18, 2026
36 checks passed
@submariner-bot
Copy link
Copy Markdown
Contributor

🤖 Closed branches: [z_pr3902/tpantelis/fix-stale-bot-cache-issue]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-test When a PR is ready for full E2E testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants