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
Rotate the Cloudflare API token and the scheduler token by 2027-10-06 #55
The Cloudflare API token the deploy uses was rolled on 2026-11-06 and expires around 2027-11-06. When it does, every deploy fails and the site stops updating. Rotate it by 2027-10-06 to leave a month of slack.
To rotate it:
In the Cloudflare dashboard, go to My Profile > API Tokens, find the DevStream token and click Roll (or create a new one with the same permissions: Cloudflare Pages edit and DNS edit on the jamesconway.dev zone, expiring about a year out).
Run gh secret set CLOUDFLARE_API_TOKEN --env production -R devstreamhq/devstream and paste the token when it asks. The secret lives only in the production environment now.
Run the Deploy site workflow and check it's green.
If you created a new token instead of rolling, revoke the old one in Cloudflare.
Retitle this issue with the next date a year on, or open a fresh one.
Done when a deploy succeeds on the new token.
The scheduler token
The scheduler Worker (scheduler/) starts the timed workflows with a fine-grained GitHub token (devstreamhq/devstream only, Actions: Read and write). It was made on 2026-11-06 with a 1-year expiry. If it lapses, Likes, on-merge and the weekly health check stop running on time. The sweep's watchdog restarts them, but only when GitHub's own scheduler happens to fire.
changed the title [-]Rotate the Cloudflare API token by 2027-10-06[/-][+]Rotate the Cloudflare API token and the scheduler token by 2027-10-06[/+]on Nov 6, 2026
Activity
[-]Rotate the Cloudflare API token[/-][+]Rotate the Cloudflare API token by 2027-10-06[/+][-]Rotate the Cloudflare API token by 2027-10-06[/-][+]Rotate the Cloudflare API token and the scheduler token by 2027-10-06[/+]