crab release

Create and verify immutable dataset release manifests for a Git revision and its Crab pointer inventory.

Synopsis

crab release <SUBCOMMAND> [OPTIONS]

Subcommands

Examples

Create a clean-worktree manifest and publish it:

crab release create --name model-v1 --rev HEAD --output release.json
crab release create --name model-v1 --rev refs/tags/v1 --publish --json

Verify locally or against the configured repository:

crab release verify --manifest release.json
crab release verify --name model-v1 --deep

List and export releases:

crab release list --remote
crab release export --name model-v1 --output portable-release.json

release create refuses a dirty worktree unless --allow-dirty is supplied. release verify supports detached Ed25519 signatures with --signature and --public-key.

Treat creation and verification as separate evidence boundaries. Record the Git revision and output manifest, then verify that exact manifest before publishing or distributing it. --allow-dirty weakens the connection between a release and committed repository state, so use it only when the uncommitted state is an explicit part of the release record. Deep verification can require remote object reads and should run with the same repository identity used to create the manifest.