helmr deploy
helmr deploy [path] [flags]The command builds the project in Helmr’s digest-pinned Linux builder, uploads
only missing content-addressed objects, finalizes the verified bundle, and
promotes it unless requested otherwise. --bundle accepts an existing output
from helmr build and follows the same upload and verification path.
| Flag | Meaning |
|---|---|
-p, --project, -e, --env |
Target scope for a saved CLI login. |
--bundle PATH |
Deploy an existing verified bundle directory. |
--skip-promotion |
Finalize without making the Deployment current. |
--idempotency-key KEY |
Stable deployment-finalization key. |
--json |
Emit progress as JSON lines. |
The install command, build secrets and build environment are
build settings in helmr.config.ts, which the command evaluates
once on this machine (Node.js 22 or newer required).
Human progress is written to stderr and the final version to stdout. After
promotion, stderr also lists each restored Agent and each trigger that waits for
a Slack connection; with --json, the deployment_result line carries them as
restored_agents and waiting_triggers. The Control Plane never installs
dependencies or rebuilds the uploaded artifacts.
Uploads use the configured Helmr origin with current authorization. When upload
capacity is busy, the CLI honors Retry-After within the per-object deadline.
Each object has a three-hour deadline, including capacity retries, and fails
after two minutes without upload progress. Server and ingress limits apply
independently.