Local Runs

For local testing, pass the working tree explicitly. This keeps unpushed edits available to Dagger and avoids relying on a remote Git ref that does not contain your latest changes.

RUSH_DELIVERY_MODULE=github.com/BootstrapLaboratory/rush-delivery@v0.6.7

dagger -m "${RUSH_DELIVERY_MODULE}" call workflow \
  --repo=. \
  --git-sha="$(git rev-parse HEAD)" \
  --event-name=manual \
  --force-targets-json='[]' \
  --environment=prod \
  --dry-run=true \
  --toolchain-image-provider=off \
  --rush-cache-provider=off \
  --source-mode=local_copy

For local PR-style validation only:

dagger -m "${RUSH_DELIVERY_MODULE}" call validate \
  --repo=. \
  --event-name=pull_request \
  --pr-base-sha="$(git merge-base HEAD origin/main)" \
  --source-mode=local_copy

For a local package-release dry-run:

dagger -m "${RUSH_DELIVERY_MODULE}" call release-packages \
  --repo=. \
  --git-sha="$(git rev-parse HEAD)" \
  --dry-run=true \
  --toolchain-image-provider=off \
  --rush-cache-provider=off \
  --source-mode=local_copy

This reads .dagger/release/npm.yaml, runs the release build lifecycle, and executes the non-publishing Rush publish path. It does not require NPM_TOKEN, does not push the generated version commit, and does not publish packages.

Avoid live package publishing from a local workstation unless you are deliberately testing the release path with disposable packages. Live package release expects Git source mode, release env credentials, and a clean CI-style source ref.

Keep live deploy credentials out of source. If a local live deploy needs files such as cloud credentials, pass them through a runtime files directory and refer to them from target metadata.

For deployment and release metadata, see Metadata contracts. For workflow shape and release behavior, see the Workflow Guide.