Repository navigation
feat(actions): support cache-mode - #40343
Draft
silverwind wants to merge 2 commits into
Draft
silverwind wants to merge 2 commits into
silverwind wants to merge 2 commits into
Conversation
…kflows GitHub's `cache-mode` key narrows a workflow's or job's cache access, or opts a low-trust trigger back into saving caches. The job payload dropped it, so runners could never honor it. A job calling a reusable workflow now also caps the cache access of the called jobs, as on GitHub, and a called job asking for more fails the expansion. Assisted-by: Claude Code:claude-opus-5-5
silverwind
marked this pull request as draft
November 12, 2026 13:21
Assisted-by: Claude Code:claude-opus-5-5
cache-mode to runners and cap it for called workflowscache-mode
This branch has not been deployed
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 free
to 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.
Forward GitHub's
cache-modekey in job payloads so runners can honor it, and cap the cache access of reusable workflow jobs at their caller's explicitcache-modeas GitHub does, failing the expansion when a called job asks for more. The runner makes low-trust triggers such aspull_request_targetandissue_commenton the default branch read-only by default, andcache-modeis how a workflow overrides that.The actionslib change must be merged and released first, this pins its commit until then.
actionslib: https://gitea.com/gitea/actionslib/pulls/33
runner: https://gitea.com/gitea/runner/pulls/1412
Assisted-by: Claude Code:claude-opus-5-5