You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b6e70ce
Browse filesBrowse the repository at this point in the historyBrowse files
fix(cli): forward CF Access headers on the OIDC token exchange (review)
The GitHub Actions OIDC → deploy-token exchange POSTs to
$VOID_API_URL/auth/github-oidc before any PlatformClient exists, so it
sent only Content-Type. When VOID_API_URL targets the Access-gated
staging API, Cloudflare Access rejected the request at the edge before
/auth/github-oidc could mint the deploy token.
Mirror every other CLI → Void-API call: call ensureCloudflaredToken(apiUrl)
and spread cfAccessHeaders(process.env) on the POST. Both no-op for the
prod/ungated path (no CF Access env, host not gated), so this is a safe
defense-in-depth change. The GitHub OIDC GET (token.actions.githubusercontent.com)
is untouched — CF Access headers belong only to the Void API.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments