Migrate Forest website to Workers Build

Open
#7,648 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, javascript
Domain
ci-cd, cloud, devops

Research direction

The issue is to migrate the forest-website deployment from Cloudflare Pages Direct Upload to Workers Build. Start by examining the linked PR (https://github.com/ChainSafe/forest-website/pull/184) to understand the current setup. The main steps involve adding a wrangler.jsonc configuration file, updating package.json to include wrangler, and configuring the Cloudflare dashboard for Workers Builds. Test locally with yarn build && npx wrangler dev and a dry-run deploy. The completion criteria is a successful migration with the custom domain attached to the new Worker.

Written by the indexing model from the issue text.

Description

Type: Task

Summary

The action we were relying on is deleted, so now we have to do some manual dance because we're stuck on Direct Upload.

https://github.com/ChainSafe/forest-website/pull/184

This works, but a cleaner solution would be to migrate to something that CF really supports and doesn't put traps on.

Completion Criteria

  • Migrate Forest website to Workers Build

Additional Links & Resources

https://developers.cloudflare.com/workers/static-assets/migration-guides/migrate-from-pages/
https://developers.cloudflare.com/workers/ci-cd/builds/configuration/
https://developers.cloudflare.com/workers/ci-cd/builds/git-integration/

Claude's migration steps (unverified, treat with caution)

Prerequisites (verified)

  • chainsafe.io runs on Cloudflare nameservers (gene/toby.ns.cloudflare.com). Required — Workers custom domains don't support external DNS with a CNAME, unlike Pages. This was the likeliest blocker; it's fine.
  • No functions/, no _headers, no _redirects. Nothing Pages-specific to port.
  • out/404.html exists, so 404 handling maps cleanly.

Steps

  1. Add wrangler.jsonc at repo root. Assets-only Worker, so no main and no ASSETS binding:
    {
    "name": "forest-website",
    "compatibility_date": "2026-09-22",
    "assets": {
    "directory": "./out",
    "not_found_handling": "404-page"
    }
    }

  2. Add wrangler to devDependencies. Verify locally before touching anything remote: yarn build && npx wrangler dev (port 8787, not Pages' 8788), then npx wrangler deploy --dry-run.

  3. In the Cloudflare dashboard, create the Worker and connect the GitHub repo via Workers Builds. Settings:

    • build command yarn build
    • deploy command npx wrangler deploy
    • preview deploy command npx wrangler versions upload (this is what non-production branches get)
    • enable non-production branch builds, so Dependabot branches keep getting previews
    • build variable NODE_VERSION=22 — same wrangler requirement that just failed your run
  4. Confirm it works on *.workers.dev while Pages still serves production. No user impact yet.

  5. Cut over the domain. forest.chainsafe.io can only attach to one of them, so: remove it as a custom domain from the Pages project, then add it as a Custom Domain on the Worker. This is the only step with a downtime window — keep it short and do it deliberately.

  6. Delete .github/workflows/cf-deploy.yaml. Workers Builds does check runs and PR comments natively, so the whole Record GitHub deployment step disappears with it.

  7. Clean up afterwards: delete the Pages project once you're satisfied, and drop CLOUDFLARE_API_TOKEN / CLOUDFLARE_ACCOUNT_ID from the Actions and Dependabot secret stores if nothing else uses them.

Caveats worth knowing before you commit to this

  • The Deployments sidebar probably still won't come back. Docs promise check runs and PR comments; they don't mention GitHub Deployment environment records. Unconfirmed either way — I'd treat the sidebar as gone.
  • forest-landing.pages.dev dies. Preview URLs become version-scoped *.workers.dev URLs.
  • Pages environment variables don't carry over to Workers Builds; reconfigure them there.
  • Workers has no equivalent of Pages' branch deploy controls.
Dominant language
Rust
Stars
700
Forks
201
Avg merge
1d 17h
Merged PRs (30d)
65

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ChainSafe/forest

All issues in ChainSafe/forest

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.