Edge Python CI/CD

check -> wasm -> demo

Workflow	Role
_check.yml	cargo shear + clippy (host and wasm targets)
_wasm.yml	Builds and optimizes compiler_lib.wasm. On tags, attaches the .wasm to the GitHub Release
_demo.yml	Deploys demo/ to Cloudflare Pages

Cloudflare Pages

Project edge-python-demo in Direct Upload mode, where actions pushes the built demo/ via wrangler pages deploy; Cloudflare does not clone or build the repo.

• Production (main): https://edge-python-demo.pages.dev
• Previews: one URL per branch / PR

Cloudflare and GitHub Setup

# Wrangler CLI (requires Node 22+)
npx wrangler login
npx wrangler pages project create edge-python-demo --production-branch=main

Then add the secrets at Settings -> Secrets and variables -> Actions:

• CLOUDFLARE_API_TOKEN — token with Account -> Cloudflare Pages -> Edit permission. Must be created via dashboard at https://dash.cloudflare.com/profile/api-tokens.
• CLOUDFLARE_ACCOUNT_ID — printed by npx wrangler whoami, or shown in the right sidebar of any Cloudflare dashboard page.

Rotate the API token

1. Create a new token at https://dash.cloudflare.com/profile/api-tokens.
2. Update CLOUDFLARE_API_TOKEN in repo secrets.
3. Revoke the old token on the same Cloudflare page.

Releases

Pushing a v* tag triggers the pipeline and _wasm.yml uploads compiler_lib.wasm to the matching GitHub Release:

git tag v0.1.0
git push origin v0.1.0