Skip to content

workflows

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History
 
 

workflows

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
_check.yml
_check.yml
 
 
_demo.yml
_demo.yml
 
 
_runtime.yml
_runtime.yml
 
 
_runtime_check.yml
_runtime_check.yml
 
 
_wasm.yml
_wasm.yml
 
 
cli.yml
cli.yml
 
 
pipeline.yml
pipeline.yml
 
 

README.md

Edge Python CI/CD

deno lint -> deno test ┐
check -> wasm -> runtime -> 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
_runtime_check.yml JS-side gate: deno lint runtime/ + deno test runtime/tests/ (Playwright + Chromium driving createWorker against the CDN-deployed wasm). Independent branch, runs in parallel with the Rust pipeline; only the CDN upload below blocks on it
_runtime.yml Bundles runtime/ + compiler_lib.wasm and deploys them to Cloudflare Pages
_demo.yml Hashes compiler_lib.wasm into version.json (cache-busting) and deploys demo/ to Cloudflare Pages
cli.yml Standalone (not part of the pipeline above): builds and tests cli/; on main pushes also publishes the release binary + install.sh to GitHub Pages

Cloudflare Pages

Two Direct Upload projects, Actions pushes prebuilt directories via wrangler pages deploy; Cloudflare doesn't clone or build.

Project Source Production URL
edge-python-demo demo/ (wasm hashed for version.json, not bundled) https://edge-python-demo.pages.dev
edge-python-runtime runtime/ + bundled compiler_lib.wasm https://edge-python-runtime.pages.dev

Both deploys run only on pushes to main (gated in pipeline.yml) and are pinned to the production main branch in _runtime.yml / _demo.yml. PRs and tags never deploy; the next main push refreshes both projects.

Cloudflare and GitHub setup

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

Repo secrets (Settings -> Secrets and variables -> Actions):

Rotate: create new token -> update secret -> revoke old token.

Releases

Pushing a v* tag triggers the pipeline; _wasm.yml uploads compiler_lib.wasm to the matching Release. Tag must match workspace version.

  1. Bump version under [workspace.package] in root Cargo.toml (every crate inherits via version.workspace = true). Run cargo check to refresh Cargo.lock, commit.
  2. Tag and push:
git tag v0.1.0
git push origin v0.1.0

On tag push: _check lints, _wasm builds and optimizes the artifact and attaches it to a fresh Release with auto-generated notes. The CDN deploys (_runtime + _demo) do not run on tags; they already deployed from the preceding main push.

Nothing is published to crates.io, distribution is the .wasm on the Release. starter-module carries its own version and isn't bumped with the workspace.

Consumer crates pick up the release automatically: compiler/Cargo.toml declares links = "compiler_lib" and compiler/build.rs downloads <repository>/releases/download/v<version>/compiler_lib.wasm into OUT_DIR. Downstreams read DEP_COMPILER_LIB_WASM in their own build.rs, see root README. Tag bumps flow via cargo update.

Gated behind the default-on prebuilt feature. Producer-side steps (_check, _wasm) pass --no-default-features to avoid fetching the asset that this same pipeline uploads later.