# Monthly release of Bitrise CLI tools and summary of updates (August, 2017) - CLI v1.8.0

**URL:** <https://discuss.bitrise.io/t/monthly-release-of-bitrise-cli-tools-and-summary-of-updates-august-2017-cli-v1-8-0/2447>\
**Category:** Changelog\
**Tags:** bitrise-cli, bitrise-tools, announcements\
**Created:** [August 8, 2017, 10:41am UTC](https://discuss.bitrise.io/t/monthly-release-of-bitrise-cli-tools-and-summary-of-updates-august-2017-cli-v1-8-0/2447 "2017-08-08T10:41:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![godreikrisztian](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/godreikrisztian/32/22_2.png) [@godreikrisztian](https://discuss.bitrise.io/u/godreikrisztian)\
**Post date:** [August 8, 2017, 10:41am UTC](https://discuss.bitrise.io/t/monthly-release-of-bitrise-cli-tools-and-summary-of-updates-august-2017-cli-v1-8-0/2447/1 "2017-08-08T10:41:21Z")

</div>

> We ship a new bitrise cli version on the second Tuesday of every month.  
> The new release will be available on the [bitrise.io](https://www.bitrise.io)  
> virtual machines on the weekend after the CLI release,  
> unless we discover a serious bug / regression.

Read on to learn more about this month’s [Bitrise CLI](https://github.com/bitrise-io/bitrise) release and about the changes around bitrise tools and steps.

* * *

## New version of Bitrise CLI ([1.8.0](https://github.com/bitrise-io/bitrise/releases/tag/1.8.0))

**`bitrise plugin update` command’s log fix**

From now on `bitrise plugin update` command will print which plugin is being updated.

```auto
$ bitrise plugin update

Updating plugin analytics
No new version available
Updating plugin init
No new version available
Updating plugin step
No new version available
Updating plugin workflow-editor
No new version available

```

**`bitrise run WORKFLOW` command’s log update**

`bitrise run WORKFLOW` command prints the workflow stack to better understand which workflows will run in what order.

```auto
Running workflows: BEFORE_WORKFLOW_1 -> BEFORE_WORKFLOW_2 --> WORKFLOW --> AFTER_WORKFLOW_1 --> AFTER_WORKFLOW_2

```

**Bitrise Tools update**

- min envman version: [1.1.6](https://github.com/bitrise-io/envman/releases/tag/1.1.6)
- min stepman version: [0.9.33](https://github.com/bitrise-io/stepman/releases/tag/0.9.33)

**Bitrise Plugins update**

- default init plugin version: [0.9.7](https://github.com/bitrise-core/bitrise-plugins-init/releases/tag/0.9.7)
- default workflow-editor plugin version: [1.0.13](https://github.com/bitrise-io/bitrise-workflow-editor/releases/tag/1.0.13)
- default analytics plugin version: [0.9.10](https://github.com/bitrise-core/bitrise-plugins-analytics/releases/tag/0.9.10)

**Bitrise Model’s version bumped to 4**

Meta field (`meta`) added to `EnvironmentItemOptionsModel`, read more on `New version of Envman` section of the Changelog.

* * *

## New version of Stepman ([0.9.33](https://github.com/bitrise-io/stepman/releases/tag/0.9.33))

Go dependencies update.

* * *

## New version of Envman ([1.1.6](https://github.com/bitrise-io/envman/releases/tag/1.1.6))

**Meta field (`meta`) added to `EnvironmentItemOptionsModel`**

This property of the environment options is used to define extra options without creating a new [envman](https://github.com/bitrise-io/envman) release.

The **bitrise-cli** does not use `meta` field directly, but other tools can use this property to expand the environment options.

For example the `bitrise.io` website will use the `meta` field to define if secret environment variables should be used in pull request triggered builds or not.

```auto
.bitrise.secrets.yml

envs:
- MY_SECRET_ENV: secret value
  opts:
    meta:
      is_expose: true

```

* * *

## Step updates

- **cache-push 1.1.4:**
  - fixing the error in case a file is to be cached and also ignored

- **certificate-and-profile-installer 1.8.7:**
  - print installed certificate’s expire date

- **openstf-disconnect 0.0.2:**
  - description and summary typo fixes
  - step tests updated

- **xcode-test 1.18.7:**
  - fix for 10.3.1 os version
  - update generated screenshot names: `Screenshot_uuid.png` → `start_date_time_title_uuid.png`

- **xcode-archive 2.1.0:**
  - the step will not fail if no dsyms generated during the build

- **android-sdk-update 1.0.6:**
- **git-clone 3.5.1:**
  - better error message if pr fetch failed

- **aws-device-farm-runner 0.0.6:**
- **gradle-runner 1.7.6:**
  - retry gradle command on `Failed to find target with hash string` and `Failed to find Build Tools revision` errors
  - updated project type tags
  - lockfile renamed
  - added dependency lockfile

- **gradle-unit-test 1.0.3:**
  - merge pull request #6 from DroidsOnRoids/optional\_buildfile\_yml
  - step.yml updated to match build file requirement changes

- **project-scanner 1.5.2:**
  - react native project in subdir fix & test
  - step version updates
  - React Native project type support

- **slack 2.6.1:**
  - add option for Linkifying user name and channel name