UiPath CLI user guide

Last updated May 7, 2026

uip maestro pack

uip maestro pack packages a Maestro project directory into a .nupkg ready to publish to Orchestrator as a Process Orchestration release.

Synopsis

uip maestro pack <projectPath> <outputPath> [-n <name>] [-v <version>]
uip maestro pack <projectPath> <outputPath> [-n <name>] [-v <version>]

Honors global options. Exit codes follow the standard contract.

Arguments

<projectPath> (required) — path to the Maestro project directory (must contain project.uiproj, a .bpmn, and the metadata files created by init).
<outputPath> (required) — output directory where the .nupkg will be written.

Options

-n, --name <name> — package name. Defaults to the project folder name.
-v, --version <version> — package version. Defaults to 1.0.0.

Examples

# Pack with defaults
uip maestro pack ./invoice-orchestration ./dist

# Pack with an explicit version
uip maestro pack ./invoice-orchestration ./dist --version 1.2.0
# Pack with defaults
uip maestro pack ./invoice-orchestration ./dist

# Pack with an explicit version
uip maestro pack ./invoice-orchestration ./dist --version 1.2.0

Data shape (--output json)

{
  "Code": "MaestroPack",
  "Data": {
    "Package": "invoice-orchestration@1.2.0",
    "Output":  "./dist/invoice-orchestration.processOrchestration.ProcessOrchestration.1.2.0.nupkg"
  }
}
{
  "Code": "MaestroPack",
  "Data": {
    "Package": "invoice-orchestration@1.2.0",
    "Output":  "./dist/invoice-orchestration.processOrchestration.ProcessOrchestration.1.2.0.nupkg"
  }
}

The generated .nupkg filename encodes <name>.processOrchestration.ProcessOrchestration.<version>.nupkg.

Was this page helpful?

PREVIOUSinit

NEXTdebug

UiPath CLI user guide

Synopsis​

Arguments​

Options​

Examples​

Data shape (--output json)​

See also​