mistralai/cli cli/v0.14.0

mistral CLI v0.14.0

Repository: mistralai/cli

Tag: cli/v0.14.0

Published: 2026-10-27T17:42:59Z

Prerelease: no

Release notes:

Changed

• mistral apps capability publish refuses a capability folder that would

pack a .env or .env. file, such as a committed .env.local, since it may hold secrets. It names each file and says how to fix it; with --all, that folder's row fails (env_file) and the others go on. .env.example, .env.sample and .env.template are published as they are.

• When an organization admin disables a whole managed capability, mistral apps install

and capability add say that none of its versions can be installed, instead of suggesting another version.

• mistral apps deploy --name refuses a name the apps API would not accept

as it stands, and says what an app name can contain. It used to change the name, so --name hello-first.last created hello-first-last. A deploy to the app mistral.json already points at still ignores --name.

Fixed

• mistral init, mistral apps init, mistral workflows init,

mistral apps registry add and mistral apps registry update commit with the name and email from your git config, so GitHub can verify the commits you sign. They commit as mistral apps only when git config is missing user.name or user.email.

• mistral apps deploy signs the commit of mistral.json it pushes whenever

git config sets user.signingkey, so people who sign on request no longer get an unsigned commit pushed. When the key cannot sign, mistral.json is left uncommitted with a warning.

• When a module fails to deploy, mistral apps deploy prints the last lines

of its build logs if the build failed, or of its runtime logs otherwise, and the apps logs command it suggests adds --build for a failed build. The --json report carries the same lines in the module's logs.