- 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 codedapp publish
Syntax and options for `uip codedapp publish`, which uploads a `.nupkg` to UiPath and registers the coded app.
uip codedapp publish uploads a packaged .nupkg to UiPath and registers the coded app. It reads packages from --uipath-dir (default ./.uipath); pass --name (and optionally --version) to publish non-interactively, otherwise the tool prompts. --type controls whether the package registers as a Web app or an Action — when omitted, it is auto-detected from action-schema.json in the current directory (Action when present, Web otherwise), with an interactive confirm before switching to Action.
Synopsis
uip codedapp publish [options]
uip codedapp publish [options]
Options
| Flag | Description |
|---|---|
-n, --name <name> | Package name (non-interactive). |
-v, --version <version> | Package version (requires --name). |
-t, --type <type> | App type: Web or Action. No static default — auto-detected from action-schema.json (Action if present, Web otherwise); interactive sessions get a confirm before switching to Action. |
--tenant-feed | Publish into the tenant package feed. |
--personal-workspace | Publish into the current user's Personal Workspace feed instead of the tenant feed. |
--folder-path <path> | Publish into the package feed of this folder, by display name or fully qualified path. A folder with its own feed resolves to that feed; a folder that reads from the tenant feed resolves to the tenant feed. A name that matches more than one folder is refused. |
--folder-key <key> | Publish into the package feed of the folder with this key. A folder that reads from the tenant feed publishes to the tenant feed. |
--feed-id <id> | Publish into this exact Orchestrator feed ID. uip or feeds list lists the feeds. |
--uipath-dir <dir> | Directory containing the packages to publish. Default: ./.uipath. |
--base-url <url> | UiPath base URL (auth override). |
--org-id <id> | Organization ID (auth override). |
--org-name <name> | Organization name (auth override), used in place of --org-id when the ID is not provided. |
--tenant-id <id> | Tenant ID (auth override). |
--tenant-name <name> | Tenant name (auth override). |
--access-token <token> | Access token (auth override). |
Feed selection
--tenant-feed, --personal-workspace, --folder-path, --folder-key, and --feed-id each pick the feed to publish into. At most one of them can be passed; two are refused. A feed option given an empty value, such as an unset CI variable, is refused instead of falling back to the tenant feed.
With none of them, an interactive run offers a feed picker, and a non-interactive run publishes into the tenant feed.
The package must be in the feed of the folder the app is deployed into. Orchestrator looks the package up in that folder's feed, so a package in the tenant feed is not visible from a folder that has its own feed.
Examples
# Non-interactive publish of a specific version
uip codedapp publish --name "MyApp" --version "1.0.0"
# Register as an Action app instead of a Web app
uip codedapp publish --name "MyApprovalAction" --type Action
# Publish from a non-default packages directory
uip codedapp publish --name "MyApp" --uipath-dir ./packages
# Publish into the current user's Personal Workspace feed
uip codedapp publish --name "MyApp" --personal-workspace
# Publish into the feed of the folder the app is deployed into
uip codedapp publish --name "MyApp" --folder-path "Shared/Finance"
# CI: publish into an exact feed, without the picker
uip codedapp publish --name "MyApp" --version "1.0.0" --feed-id <feed-id>
# Non-interactive publish of a specific version
uip codedapp publish --name "MyApp" --version "1.0.0"
# Register as an Action app instead of a Web app
uip codedapp publish --name "MyApprovalAction" --type Action
# Publish from a non-default packages directory
uip codedapp publish --name "MyApp" --uipath-dir ./packages
# Publish into the current user's Personal Workspace feed
uip codedapp publish --name "MyApp" --personal-workspace
# Publish into the feed of the folder the app is deployed into
uip codedapp publish --name "MyApp" --folder-path "Shared/Finance"
# CI: publish into an exact feed, without the picker
uip codedapp publish --name "MyApp" --version "1.0.0" --feed-id <feed-id>
Data shape (--output json)
{
"Code": "PublishCompleted",
"Data": { "message": "Package published successfully." }
}
{
"Code": "PublishCompleted",
"Data": { "message": "Package published successfully." }
}
Related
- uip codedapp pack — produce the
.nupkgthatpublishuploads. - uip codedapp deploy — deploy or upgrade the app once it's published.