Skip to content

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

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#2049
tpantelis merged 2 commits intosubmariner-io:develfrom
tpantelis:fix-stale-bot-cache-issue

Conversation

@tpantelis
Copy link
Copy Markdown
Contributor

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

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_pr2049/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

Warning

Rate limit exceeded

@tpantelis has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 29 minutes and 48 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.


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.

@skitt skitt enabled auto-merge (rebase) February 18, 2026 08:45
@tpantelis
Copy link
Copy Markdown
Contributor Author

@coderabbitai approve

@tpantelis tpantelis disabled auto-merge February 18, 2026 18:22
@tpantelis tpantelis merged commit ca5b9e6 into submariner-io:devel Feb 18, 2026
23 checks passed
@submariner-bot
Copy link
Copy Markdown
Contributor

🤖 Closed branches: [z_pr2049/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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants