@uipath/cli-meta

@uipath/cli-meta

Source metadata for UiPath CLI version selection.

cli-versions.json maps UiPath environments to the CLI version line that should be used for that environment. The CLI version sync flow consumes this data to align installed CLI versions after login and during daily auto-update checks. package.json owns the package metadata and aligned base version.

How the CLI consumes this map, and how it fits the wider release/pin model, is documented in docs/reference/versioning.md.

Schema

{
    "schemaVersion": 1,
    "generated_at": "2026-06-08T12:23:37Z",
    "environments": {
        "alpha": {
            "cliVersion": "1.2"
        }
    }
}

• schemaVersion is the metadata schema version understood by the CLI.
• generated_at is the UTC timestamp for the generated metadata.
• environments maps environment names to their CLI version line.
• cliVersion is a major/minor version pin.

Publishing

Changes to the cli-meta source files trigger the publish-cli-meta job in .github/workflows/publish-npm.yml. That job validates the JSON and publishes the @uipath/cli-meta package.

The source package.json is private so it is not published by the broad package publish loop. The publish-cli-meta job stages a publishable package from these source files and derives the npm version from the package version plus a UTC timestamp suffix:

<package-json-version>-YYYYMMDDTHHMMSSZ

For example, package version 1.196.0 publishes as a snapshot version such as 1.196.0-20260608T122337Z.