Skip to main content

uip rpa-legacy package

uip rpa-legacy package packs an RPA project into a deployable .nupkg using the legacy uipcli packager directly. For new pipelines that do not depend on a legacy-only feature, prefer the cross-platform uip rpa pack — it accepts the same project and produces an equivalent NuGet package on Linux, macOS, or Windows.

Windows-only — see the overview warning.

Synopsis​

uip rpa-legacy package <project-path> -o <output-dir> [options]
  • <project-path> (required) — Path to the RPA project or project.json.

Options​

FlagDescription
-o, --output <path>Output directory for the generated .nupkg.
-v, --version <version>Package version.
--auto-versionAuto-generate package version.
--output-type <type>Force output type (Process, Library, Tests, Objects).
--split-outputSplit output into runtime and design libraries.
--repository-url <url>Source repository URL.
--repository-commit <sha>Source repository commit SHA.
--repository-branch <branch>Source repository branch.
--repository-type <type>Source repository type.
--project-url <url>Automation Hub project URL.
--release-notes <text>Release notes for the package.
--timeout <seconds>Timeout in seconds for the operation.

Examples​

# Pack a project to ./out with an explicit version
uip rpa-legacy package ./MyProject -o ./out --version 1.4.0

# Pack a library with auto-versioning and split runtime/design output
uip rpa-legacy package ./MyLibrary -o ./out \
    --output-type Library --auto-version --split-output

# Pack with VCS metadata embedded for traceability
uip rpa-legacy package ./MyProject -o ./out \
    --version 1.4.0 \
    --repository-url https://github.com/acme/automations \
    --repository-branch main \
    --repository-commit a1b2c3d4e5f6 \
    --release-notes "Adds invoice routing rules."

See also​