Skip to content

Reject GitHub cache requests throughout release jobs - #770

Draft
zaniebot wants to merge 1 commit into
zb/release-cache-proxy-actionfrom
zb/release-cache-proxy
Draft

Reject GitHub cache requests throughout release jobs#770
zaniebot wants to merge 1 commit into
zb/release-cache-proxy-actionfrom
zb/release-cache-proxy

Conversation

@zaniebot

Copy link
Copy Markdown
Collaborator

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-cache behavior 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 and release-prepare.yml are unchanged. This adds default-deny protection; Windows still lacks the action's direct-IP firewall restriction. The action pin points to the source draft in uv-dev and should move to the corresponding uv commit when the source is landed upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants