Commit Graph

2 Commits

  • fix(deploy): run Cloudflare deploys from verified artifacts behind pinned targets
    Repository code outside .github/ needs no review, but every deploy job held a
    Cloudflare token strong enough to write any Worker on the account (the data
    sync Workflow PUT has no per-Worker permission). A dev merge could therefore
    overwrite production Workers.
    
    Split each service into a build job with no environment, secrets, or OIDC token
    that uploads a SHA256SUMS artifact, and a deploy job in dev|production that
    checks out only .github/release/, verifies the artifact against the build job's
    digest, installs the cf/wrangler CLI pinned here, and runs only deploy-*.sh.
    
    The deploy scripts treat the artifact as data and refuse it unless its resolved
    config equals the pinned target in .github/release/targets/ exactly: Worker
    names, routes, custom domains, crons, Workflow names, and bindings. For cf
    services the pinned config is what cf reads. That is what makes an account-wide
    token safe, and it keeps production out of reach of a dev merge.
    
    Adds the cf 1.0.0-beta.12 and wrangler 4.110.0 lockfiles the deploy jobs
    install with npm ci --ignore-scripts.