registry-render command reference
Governed, byte-stable PDF documents from registry data, rendered with Typst.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.1 and catalog SHA-256 61bebbb88fe15e4da92e2b0adbca0cd5b1a47b8eac38f4b91a15095011368a43. Hidden implementation commands are omitted.
registry-render <COMMAND>Commands
Section titled “Commands”| Command | Description |
|---|---|
init | Scaffold a working starter bundle |
check | Check a bundle or package and a runtime file offline, reporting every finding |
validate | Dry-run request data against a document’s schema, without rendering |
package | Build a new deployment package with the shared checksum envelope |
keygen | Generate a seal key and the certificate request for its seal certificate |
compile | Render one document offline |
serve | Serve the HTTP rendering API (see the runtime YAML) |
healthcheck | Probe a running server’s /health |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
-h, --help | No | n/a | n/a | n/a | Print help |
-V, --version | No | n/a | n/a | n/a | Print version |
Generation contract
Section titled “Generation contract”After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.