Skip to content
Cello
Esc
↑↓navigate↵open⌘Jpreview
On this page

Maintainers and contributing

How Cello is branched, reviewed, and released — and how to run the test suite locally.

Cello is agent-run: every change lands through a pull request into main (rebase merges only), required checks stay green on both architectures, and an independent review — explicitly diffing .github/ and Dockerfile — records its verdict before merge. upstream/main mirrors upstream denoland/celld and carries no patches; upstream fixes are ported by hand. Releases are cut by pushing v<semver> tags; tags are never moved or reused.

The full process, including what goes where and the license notices, lives in CONTRIBUTING.md at the repo root. This page adds only the local test how-to.

Run the test suite locally

Run the suite the way CI runs it:

cargo test --profile ci --locked

If the esbuild on your PATH is a wrapper script (for example a mise shim), bundling tests fail with a permission error. Point the child at the real binary instead:

CELLO_ESBUILD=/path/to/real/esbuild cargo test --profile ci --locked

The Docker test stage needs no knob: it installs the real esbuild at /usr/local/bin/esbuild.

Every test spawn goes through the hermetic helper in crates/cello/tests/common/mod.rs. It clears the inherited environment and rebuilds it from PATH, TMPDIR, a fixture-scoped HOME, and CELLO_ESBUILD when set — nothing else. A stray CELLD_* in your shell makes cello refuse to start, which is how the harness proves the child sees nothing ambient. CI runs the suite in a hostile environment — CELLD_HERMETIC_CANARY=1 set and CELLO_DEV_STATE pointed nowhere writable — so a test whose outcome depends on the harness environment, or a spawn that bypasses the cleared environment, fails in CI instead of on your machine.

Was this page helpful?