Skip to content

ci(deploy): state the token scope without the deploying account's identifiers #200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
debuggingfuture merged 1 commit into from
Oct 16, 2026
Merged

ci(deploy): state the token scope without the deploying account's identifiers #200

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions .github/workflows/deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,9 @@ name: deploy
# `workflow_dispatch` with `target: substrate` stops after the canary, so a
# security patch to the substrate never queues behind a product release.
#
# CREDENTIALS. `CLOUDFLARE_API_TOKEN` — account-scoped to FractalBox
# (c91d52c2…), no zone resources: Workers Scripts:Edit, Workers KV:Edit,
# Workers R2:Edit, D1:Edit, Containers:Edit, Account Settings:Read.
# Created 2026-08-06 · dash.cloudflare.com/profile/api-tokens · no expiry.
# CREDENTIALS. `CLOUDFLARE_API_TOKEN` — scoped to the deploying org's account,
# no zone resources: Workers Scripts:Edit, Workers KV:Edit, Workers R2:Edit,
# D1:Edit, Containers:Edit, Account Settings:Read.
# Scope is recorded here because GitHub secrets have no comment field and a
# Cloudflare token cannot report its own policies — reading them needs a
# *second* token with API Tokens:Read, so an undocumented token's grants are
Expand Down
Loading