Repository navigation
Traverse v0.10.1
Traverse v0.10.1
Release candidate for the v0.10 line.
Traverse v0.10.1 is a compatibility-preserving patch release for the public
runtime, browser embedder, and CLI authoring path.
Fixes
- The native
WasmExecutoraccepts WASI preview1proc_exit(0)as successful
completion and still rejects nonzero process exits. Capabilities that write a
JSON result and then exit successfully now return that result as intended. - The web embedder supplies deterministic denied shims for the approved
traverse_host.emit_eventandtraverse_host.connector_invokeimports. This
lets ABI-valid modules load while preserving the browser host's no-ambient-
connector-authority boundary. traverse-cli app newwritesapp.manifest.json, matching the documented
application-bundle convention.
Upgrade notes
The Rust crate APIs and traverse-cli binary name are unchanged. Existing
applications need no migration. Browser capabilities that declare the approved
connector imports now load deterministically; connector calls remain denied
until an activated binding adapter is supplied by a host integration.
Validation
Release preparation must pass these local gates before tagging:
cargo build --workspace
cargo test --workspace
bash scripts/ci/repository_checks.sh
bash scripts/ci/spec_alignment_check.sh
bash scripts/ci/coverage_gate.sh
TRAVERSE_PUBLISH_DRY_RUN=1 TRAVERSE_PUBLISH_NO_VERIFY=1 bash scripts/ci/publish_crates.shThe tagged commit must pass the GitHub version-guard, repository-checks,
coverage-gate, and stress-test jobs before the tag-triggered crates.io
publish job can run.
Release steps
Per the release process, from this clean release
candidate after CI is green:
bash scripts/ci/bump_version.sh 0.10.1
git push origin codex/release-v0.10.1:main
git push origin v0.10.1The tag push triggers the guarded crates.io publication workflow. The
publication requires explicit manual approval under the Traverse constitution.