- Release Notes
- Introduction
- Governance
- Source Control
- CI/CD Pipelines
- Feeds Management
- Logging
UiPath CLI Release Notes
Check out the release notes for the UiPath CLI under this section.
Release date: October 11, 2024
.NET 8 support
CLI 24.10.0 now supports .NET 8, generating packages with .NET 8 dependency.
Packager 24.10
uipcli 24.10
uses UiPath.Workflow.StandaloneAnalyzer.24.10
and UiPath.Studio.ProjectPackager.24.10
dependencies.
Enhanced workflow analysis
--governanceFilePath
parameter. The parameter allows you to directly pass file paths to your uipcli package analyze
task.
Create process with custom name
--processName
/--processNames
parameters with uipcli package deploy
task.
Improved CLI help menu
We have made multiple enhancements to the CLI help menu for better user interpretation and readability.
Release date: May 24, 2024
Added release notes argument
releaseNotes
argument.
New retryCount
parameter
Allows you to retry any failed test for a certain number of times.
Disabling built-in feeds
disableBuiltInNugetFeeds
argument.
nuget.config
file. For more details, refer to this section.
Release date: December 21, 2023
Telemetry
UIPATH_EXTENSIONS_CLI_TELEMETRY_ENABLED
environment variable on the agent executing the tasks with the value set to False
. If the agent is isolated from the internet (onPrem), telemetry is not sent.
Inline help for uipcli run
command
uipcli run "args_path.json"
.
This is another way of running any task.
UiPath Official feed update
https://pkgs.dev.azure.com/uipath/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json
.
Packager 23.10
uipcli 23.10
uses UiPath.Workflow.StandaloneAnalyzer.23.10
and UiPath.Studio.ProjectPackager.23.10
dependencies.
Library split
nupkg
files by setting splitOutput=true
optional argument. By default, libraries are kept in one piece to maintain backwards compatibility.
Set optional package metadata
Pack
or RunTests
from a project.json
, you can specify the following optional parameters:
RepositoryUrl
RepositoryCommit
RepositoryBranch
RepositoryType
ProjectUrl
nupkg
files.
analyzerTraceLevel
was not passed correctly to packager no matter the error level used.ignoredRules
parameter value was used incorrectly. Thus the rules specified here were not ignored.- The analyze task could not receive the
--identityUrl
and--traceLevel
parameters. - Pack task could not receive the
--libraryIdentityUrl
parameter. - Could not get dependencies from on-prem orchestrator feed when connecting with basic authentication and the user was not assigned to the shared folder. Now, when fetching dependencies, the user must at least have access to the library feeds.
Release date: 30 June 2023
- When deploying a package to
Orchestrator, a process was created even if the
--createProcess
parameter wasn't specified. Now, you can control the creation of the process, by setting the--createProcess
parameter to either-c true
, or-c false
. - Fixed issues with the packager to streamline CLI executions.
- The Azure DevOps Plugin was unable to retrieve packages stored in Orchestrator when building workflow projects, causing difficulties when using secured networks. Now you can succesfully build projects, because the CLI manages to retrieve the packages stored in Orchestrator.
Release date: 9 December 2022
This marks the first standalone release of the UiPath CLI, allowing you to run tasks related to RPA package management and testing without the help of any plugin. To learn how to use the UiPath CLI, make sure to visit the following pages:
-
Want to have more control over which packages you can run as processes in Orchestrator? You can now choose if you want to create a process out of the package that you're deploying. To achieve this, set the following parameter for the
package deploy
task:"createProcess": false
- doesn't create a process."createProcess": true
- creates a process.
- The CLI now supports the compiling of Windows and Cross-platform projects, which enables you to run even more projects over the build agent.
- All the errors that the Packager throws at compilation can now be viewed and investigated from the console error logs.