Releases are manual and auditable during the 0.1.x phase.
The current coordinated release is tracked in the
0.1.0-beta.2 release checklist. The
completed first release remains recorded in the
0.1.0-beta.1 release checklist.
- Run TypeScript build, typecheck, tests, cross-language conformance, and package checks.
- Run Rust formatting, Clippy, all-feature tests, rustdoc with warnings denied, and package verification.
- Review packed file lists and third-party notices.
- Verify the compatibility matrix and changelogs.
- Publish protocol packages first, runtimes second, and Inspector last.
- Test each published artifact from a clean temporary consumer before promoting it to the stable release channel.
When a coordinated release bumps zenfg-snapshot, a normal cargo package -p zenfg cannot resolve the runtime's new exact optional registry dependency until
the protocol crate is published. npm run cargo:package-check covers this
interval accurately: it packages and verifies zenfg-snapshot, assembles the
exact zenfg archive, then compiles the unpacked archive outside the workspace
with the packaged protocol crate supplied through a temporary crates.io patch.
After the protocol crate is published, the release operator must also run
ordinary cargo package -p zenfg --locked --allow-dirty before publishing the
runtime.
No dual-registry automatic release tool is required for the initial series.