Skip to content

pack:publish

← Back to CLI Commands

Publish a domain pack to a registry

pnpm pack:publish

Options:

FlagDescriptionRequired
--id <packId>Pack ID to publish (resolves under —packs-root)No
--packs-root <dir>Root directory containing packs (default: the workspace pack root)No
--pack-root <dir>Direct path to pack directory (overrides —id and —packs-root)No
--registry-url <url>Registry URL (default: “https://registry.lumenflow.dev”)No
--registry-ref <ref>OCI repository name within the registry (default: the pack id)No
--token <token>Registry HTTP auth token (default: $LUMENFLOW_REGISTRY_TOKEN or $GITHUB_TOKEN)No
--identity-token <token>Sigstore OIDC identity token for keyless signing (default: $LUMENFLOW_SIGSTORE_IDENTITY_TOKEN). Required — publishing never falls back to unsigned.No
--sbom <path>Path to the required CycloneDX JSON SBOM. Its component name/version must match the pack manifest.No
--fulcio-url <url>Non-default Fulcio CA URL (advanced/air-gapped signing setups)No
--rekor-url <url>Non-default Rekor transparency-log URL (advanced/air-gapped signing setups)No
--build-type <uri>SLSA provenance build type (default: https://lumenflow.dev/build-types/pack-publish/v1)No
--builder-id <uri>SLSA provenance builder identity (default: “https://github.com/hellmai/lumenflow-dev/.github/workflows/publish.yml@refs/tags/v”)No
-f, --forceForce operationNo

← Back to CLI Commands