@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. package.json owns the package metadata and aligned base version.

Deprecated — kept for old clients only. The CLI stopped reading this map. Version policy now lives entirely in core.version (exact pin = frozen, float pin = track that line, unset = follow the latest published version on the active channel) — see docs/reference/versioning.md.

The package keeps publishing so CLIs already installed in the field, which still download it, keep resolving a line. Once those versions age out, this package and .github/workflows/publish-cli-meta.yml go away. Nothing in this repo consumes cli-versions.json any more, so editing it changes nothing for a current CLI.

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 .github/workflows/publish-cli-meta.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 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.