- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip maestro authoring
- uip maestro registry
- uip model-hub
- activities find
- activities get-default-xaml
- analyze
- analyzer-rules list
- build
- cleanup
- data-fabric-entities install
- data-fabric-entities list
- files diff
- get-library-object-repository
- get-object-repository
- init
- instances list
- pack
- packages inspect
- packages install
- packages versions
- publish
- remote
- restore
- run, debug & execution
- settings
- studio start
- templates search
- test-data add-entity
- test-data add-queue
- test-data add-variation
- tm
- uia
- validate
- workflow-examples get
- workflow-examples list
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
uip rpa pack
Syntax and options for `uip rpa pack`, which packages a UiPath Studio project into a `.nupkg` archive for upload to Orchestrator.
uip rpa pack packages a UiPath Studio project directory into a .nupkg archive that can be uploaded to Orchestrator or published to a feed. It is the modern replacement for uipcli package pack from the legacy .NET CLI. Refer to Migration — package pack for the full flag-to-flag map.
Runtime requirements
- .NET runtime must be available on the runner — the Studio packager is .NET-backed. Refer to Breaking changes — .NET runtime.
- Windows runner for Windows projects. Cross-platform Studio projects (
targetFramework: "Portable") can be packed on any OS. Windows projects (targetFramework: "Windows") require a Windows runner — the Linux and macOS workflow compilers cannot resolve Windows-only references. Windows - Legacy projects requireuip rpa-legacy, which is Windows-only by design. Refer to uip rpa overview for details.
Synopsis
uip rpa pack <project> [output-path] [options]
uip rpa pack <project> [output-path] [options]
<project>— path to the Studio project (a directory containingproject.json).[output-path]— directory where the.nupkgis written. Pass it here or as--output-path.
For the complete option list on your installed tool version, run:
uip rpa pack --help
uip rpa pack --help
The flag set is the same in concept as legacy uipcli package pack: output directory, package metadata overrides, output type, analyzer settings, and signing material. Flag names are kebab-case (--output-type, --package-version, --signing-certificate-path) rather than the PascalCase used by uipcli. Refer to Migration — package pack for the legacy-to-modern flag map.
A package packed with --output-type Library is uploaded with uip or libraries, not uip or packages.
Source and dependency options
When these flags are omitted, the project's own settings in Studio apply.
| Flag | Description |
|---|---|
--include-sources | Include source files in the package. When neither this flag nor --no-include-sources is passed, the project's Include Sources setting (stored in .project/design.json) applies, and sources are included when the project does not set it. |
--no-include-sources | Exclude source files, overriding the project's own setting. |
--skip-dependency-optimization | Skip dependency optimization. When omitted, the project's Separate Runtime Dependencies setting applies. |
Analyzer and governance options
pack runs the workflow analyzer before packaging unless you pass --skip-analyze.
| Flag | Description |
|---|---|
--skip-analyze | Skip the analysis step. |
--governance-file-path <path> | Path to a governance policy rules JSON file. When the signed-in tenant publishes an Automation Ops policy, that policy applies and this file is ignored with a warning. When the tenant publishes none, or the answer cannot be established, this file applies. |
--governance-file-type <type> | How a supplied policy file is read: Default, AutomationOps, or Studio. With a policy file and no type, pack reads it as Studio. |
--policy-file <path> | Alias for --governance-file-path. |
--policy-file-type <type> | Alias for --governance-file-type. |
--governance-product <product> | Product whose published Automation Ops policy is resolved, for example Development, Business, or StudioWeb. Defaults to Development. Must not be empty. |
--ignored-rules <rules> | Comma-separated analyzer rule IDs whose findings are ignored, for example ST-USG-034,ST-MRD-002. Repeat the flag to add more. The rules still run, but their findings are not reported and do not fail the command. Applies on top of a governance file or the shipped rules. Not applied, with a warning, when the signed-in tenant publishes an Automation Ops policy. |
Examples
# Pack without source files, ignoring two analyzer rules
uip rpa pack ./MyProject ./out --no-include-sources --ignored-rules ST-USG-034,ST-MRD-002
# Pack against a local policy file when the tenant publishes no policy
uip rpa pack ./MyProject ./out --governance-file-path ./policies/governance.json
# Pack without source files, ignoring two analyzer rules
uip rpa pack ./MyProject ./out --no-include-sources --ignored-rules ST-USG-034,ST-MRD-002
# Pack against a local policy file when the tenant publishes no policy
uip rpa pack ./MyProject ./out --governance-file-path ./policies/governance.json
Migration from the legacy .NET CLI
| Legacy .NET CLI | Modern CLI |
|---|---|
uipcli package pack <project> | uip rpa pack <project> |
Refer to Migration — package pack for the full flag-level map.
Related
- uip rpa analyze — run the workflow analyzer before packing.
- uip rpa restore — ensure dependencies are present on disk before packing.
- uip or packages upload — upload a
ProcessorTests.nupkgto Orchestrator. - uip or libraries upload — upload a
Library.nupkgto Orchestrator.