Uh oh!
There was an error while loading. Please reload this page.
gh-140279: Stale workflow needs 'actions: write' to update its own cache - #148165
Merged
Conversation
StanFromIreland
commented
Apr 6, 2026
Member
You can put this under #140279 (which seeks to improve its effectiveness). |
StanFromIreland
approved these changes
Apr 6, 2026
hugovk
enabled auto-merge (squash)
April 6, 2026 12:49
ezio-melotti
approved these changes
Apr 6, 2026
hugovk
commented
Apr 6, 2026
MemberAuthor
The newest one had no cache error 👍 |
hugovk
commented
Apr 7, 2026
MemberAuthor
And the next two have continued as expected: |
Safihre
commented
Apr 10, 2026
So, what is actually done with the Stale label? Does anyone look at them? |
MemberAuthor
See #116857 (comment), let's continue in core-workflow. |
ljfp pushed a commit
to ljfp/cpython
that referenced
this pull request
Apr 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Looking at the last three stale runs:
They all process the same batch:
This is because it fails to update its own cache:
According to actions/stale#1133 (comment) it needs
actions: writeto update the cache.Then the next run should be able to process the next batch.