The Bitrise CLI helps you to run your Bitrise workflows on any Mac or Linux machine, and use the same configuration on bitrise.io website — from init, setup, validate to update, run and trigger. Additionally, you can use the plugins to edit the workflow offline with a local version of the Bitrise Workflow Editor.
![](https://cdn.prod.website-files.com/5db35de024bb988f5fb4e168/661683fa16a45c8c69b72d13_638dd8727f6d26a010497094_IM1dj7qU-LnnszMgPeZI0Tj1UQBSNjkBLifD0zt6FHGQQTEA-cMsDspO44lKV-A0aYRK12bfjrxfdBMW3GkbI9EVmgbo5eurYCB5hR6gs9bJj2CrD3C-pCDxFJFFdlQhsDHDQFSipL9uGkbiGN5bH3h4JNrgnZHrCeQuMCoe8umCa3ZaFMVprcne-njFbQ.png)
Recently, we released the new version of Bitrise CLI 2.0.0. Let’s explore what’s been changed.
Install or upgrade Bitrise CLI
To install this version, run the following command:
💡TIP: For M1 machines, please note by default /usr/local/bin does not exist on M1 machines and isn't encouraged by the community over /opt/bin. Use a custom folder path or use your own bin folder path. i.e /opt/bin
After that, you need to run:
That’s all. To make sure the installed version, run the following command:
And the version should be 2.0.0
Breaking changes
The --loglevel command line parameter has been removed from the CLI.
![](https://cdn.prod.website-files.com/5db35de024bb988f5fb4e168/661683fa16a45c8c69b72d07_638dd872fe86db56759cc59d_XFLOD5POPRSCEhj9TKy8YbDldvhs845goDHUZk7X9EkkbmD0oqj-Tvwvhm_9H42x4acE8mlammuozOGzMUWIOYqds9L0dF4LAgHK_lNvBAzw9ABDZYgFPSGTozEOhO9d8gxXNok4YNR3C443AJbTrwHpNZRmNVnu929xY7W6l3ckRCoxF8W3qokRt7_h8A.png)
Use the --debug flag to enable the debug logs if necessary.
![](https://cdn.prod.website-files.com/5db35de024bb988f5fb4e168/661683fa16a45c8c69b72d0b_638dd872b7ad20c92c25e021_bZgZVum8n2Nx4pcaFe6JItr5Iok-QhMtNajfhSn2GCJUTd8pQQPW71VZ2DjxSsN5Naxu6oFPE3qmCENmv2OapOOl-5umicaBrrj4ut_QTeaO2iMuk3F0ObNoYPuO13n_zfj7tWWgzBvhL4g4D93bc0yjRFYimQjJdq_BMGDkyqsd7zulj7yFXyBTPHUcpQ.png)
Experimental feature
For structured logging, a new option was added to the run command to enable the new json logging format. To enable it, simply supply the --output-format json parameter to the run command. CLIs still use human-readable formats by default.
![](https://cdn.prod.website-files.com/5db35de024bb988f5fb4e168/661683fa16a45c8c69b72d17_638de448df3d0f9115b50f30_Screenshot%25202022-12-05%2520at%252013.29.23.png)
Small improvements
In addition, we made small improvements to make debugging easier:
- The CLI now logs any error related to step preparation. Previously, these did not show up in the build logs.
- The summary section at the end of a workflow run now has the ID of which workflow it belongs to.
![](https://cdn.prod.website-files.com/5db35de024bb988f5fb4e168/661683fa16a45c8c69b72d0f_638dd87257f7c29a657d9c90_Q8u-pgXvUUWcxBv4csviVfwMDcfmTqM_hvMIKMtfhRGKu75QqPTtEGM-8krnGGmHVFysZt82OCrCL8p-ZfW_a7UhHmFMcjrVpYW2NtQlCKsIYi4HYS96XoqwMi4WLp26VgAwr0XLpHs7sfIH8b8mcixbchGl9mpjvf5uCGRop6TgXtoj24Xb8kIO1-u5mQ.png)
- The CLI was always using master as the default branch value if none was supplied in the git:: special source step definition. This is removed and it uses the value defined in the repository.
You can give it a try and send your feedback to our discussion forums, for more information you can check the changelog of the release here.
Thank you and happy building!