slachiewicz opened a new pull request, #311: URL: https://github.com/apache/maven-gh-actions-shared/pull/311
`actions/stale` writes a `_state` cache of the items it has already processed and deletes it when the run ends. That delete needs `actions: write`, which this workflow never granted, so it fails with `Resource not accessible by integration` and the cache is never reset. Every subsequent run then reports `issue skipped due being processed during the previous run` for exactly the items carrying `waiting-for-feedback`. The result is that an issue gets marked stale once and is never closed. `apache/maven-release#1297` has carried both `waiting-for-feedback` and `Stale` since 2026-02-24; `gh cache list -R apache/maven-release` shows a single 497-byte `_state` entry created that same day and still being read. Roughly 78 repositories call this workflow, so all of them are in the same state. The stuck caches will need deleting once per repository before the bot picks the backlog up again. *This change was created with AI assistance.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
