Reject GitHub cache requests throughout release jobs - #770
Draft
zaniebot wants to merge 1 commit into
Draft
Conversation
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.
Older cache clients can restore shared GitHub Actions caches despite
ACTIONS_CACHE_MODE: none. Run the cache-denial action from #769 before other release job steps, and require its reviewed SHA and placement in the release-policy checks. The repository-and-SHA reference supports Depot runners that are too old for$/action references.Keep ordinary CI's
allow-cachebehavior unchanged, and use a full Ubuntu runner for the release-only wheel check so the proxy can install its networking rules. Existing client opt-outs andrelease-prepare.ymlare unchanged. This adds default-deny protection; Windows still lacks the action's direct-IP firewall restriction. The action pin points to the source draft inuv-devand should move to the correspondinguvcommit when the source is landed upstream.