uip flow pack

uip flow pack packages a Flow project directory into a .nupkg file ready to publish to Orchestrator.

Synopsis

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

Honors global options. Exit codes follow the standard contract.

参数

• <projectPath> (required) — path to the Flow project directory (must contain project.uiproj and at least one .flow file).
• <outputPath> (required) — output directory where the .nupkg will be written. Created if it does not exist.

选项

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

示例

# Pack with defaults (name = folder, version = 1.0.0)
uip flow pack ./invoice-flow ./dist

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

# Override the package name
uip flow pack ./invoice-flow ./dist --name Invoicing.Flow --version 1.2.0

Data shape (--output json)

{
  "Code": "FlowPack",
  "Data": {
    "Package": "invoice-flow.1.2.0.nupkg",
    "Output": "./dist/invoice-flow.1.2.0.nupkg"
  }
}

Known issue — Solution pack

When a Flow project is added to a solution (uip solution project add) and packed with uip solution pack, the resulting .nupkg inside the solution zip can be missing critical files (.bpmn, .flow, entry-points.json, bindings_v2.json).

The root cause is a non-recursive copyFiles() helper in the published @uipath/tool-flow — it silently skips the content/ and flow_files/ subdirectories. uip flow pack uses a recursive copy and is not affected.

Workaround: use uip flow pack directly to produce deployable .nupkg files until the solution pipeline is fixed.

另请参阅

• uip flow init — scaffold the project first
• uip flow validate — validate before packing
• Flow overview