Add a release cache-denial action - #769
Draft
zaniebot wants to merge 2 commits into
Draft
Conversation
zaniebot
changed the base branch from
zb/release-cache-policy
to
zb/release-cache-proxy-base
August 17, 2026 17:58
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
2 participants
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.
Release jobs can consume a poisoned GitHub Actions cache through clients that do not honor
ACTIONS_CACHE_MODE. Add an early-running action that rejects the legacy and v2 cache APIs while preserving artifact traffic. It handles GitHub's HTTPS endpoints and Depot's injected HTTP endpoints, checks that denial is active, and removes its temporary networking and certificate changes at the end of the job.Linux and macOS also restrict direct connections to the resolved cache-service addresses; Linux covers local Docker-bridge traffic. Windows provides DNS-based interception without that additional firewall restriction. This is defense in depth for trusted release actions, not credential revocation or a sandbox for malicious actions. The workflow integration is separate.