BMCLI Installation and update

The first non-empty line of the bundled changelist.txt is the sole customer product version source (for example, 1.0.0). Archive names, website release directories, VERSION, and manifest version use that three-part value. Bamboo build number and Git commit remain separate traceability fields in BUILD_INFO.json, the release manifest, and bmcli version --format=json; they are not appended as a fourth or fifth public version segment.

Recommended website bootstrap commands:

irm https://download.busmust.com/bmcli/install.ps1 | iex

curl -fsSL https://download.busmust.com/bmcli/install.sh | sh

The installer downloads the platform artifact from the release manifest, verifies SHA-256, stages a versioned copy, updates the active runtime, adds the binary directory to the user PATH, and runs bmcli ai setup. The Windows MinGW package contains only bmcli.exe and libbmapi.dll; the GCC and C++ runtimes are linked statically. It does not contain the MSVC BMAPI.dll.

bmcli version
bmcli update --check
bmcli update
bmcli update --version=1.0.0
bmcli update --check --format=json

bmcli update --check reads the latest manifest, verifies its published changelist.txt SHA-256, compares semantic versions, and displays only entries newer than the installed version. It never downloads a binary or changes the installation. bmcli update performs the same pre-check and invokes the bundled installer only when latest is newer; equal versions report up_to_date, and a local version newer than latest is not downgraded. --version=X.Y.Z explicitly selects an upgrade or rollback target. A ZIP package remains available for offline/manual deployment, but users should not manually manage PATH for normal online installation.

Source of truth: bmcli_reference.md in the BMCLI repository. Run bmcli help <category> <action> --format=json for the exact contract of the installed version.