Monthly release of Bitrise CLI tools and summary of updates (Dec)

We ship a new bitrise cli version on the second Tuesday of every month. The new release will be available on the bitrise.iovirtual machines on the weekend after the CLI release, unless we discover any serious bug/regression.

Read on to learn more about this month’s Bitrise CLI release and about the changes around Bitrise tools and steps.

New version of Bitrise CLI (1.25.0)

1. apt-get improvements

From this release, bitrise cli will call apt-get update only once per bitrise run command, to ensure apt-get dependencies are installed.

1. Some more tests and typo fixes added

1. Tools update

  • envman version bumped to 2.1.2
  • stepman version bumped to 0.10.6

2. Default plugins update

  • init plugin version bumped to 1.0.7
  • workflow-editor plugin version bumped to 1.1.42

3. Go dependencies update

New version of Stepman (0.10.6)

  • Go dependencies update

New version of Envman (2.1.2)

  • Envman will not fail in case of unknown environment option defined for an environment variable, this way later introduced options will not break earlier Envman releases.
  • Go dependencies update

New steps

  • decrypt-file 0.9.0
  • geckoboard-dashboard-build-result 0.1.0
  • zip-directory-and-export-its-path 1.0.2

Step updates

  • git-clone 4.0.13:
    • manual merge input description updated: When the Pull Request is from a GitHub or Bitbucket private fork repository set this to "no"
  • github-release 0.10.0:
    • add support for pre-release. You can set your release to a pre-release by enabling the pre_release input
  • ios-auto-provision 1.2.2:
    • tvOS profile creation issue is fixed now. It was an issue when the step created the profiles itself, it didn’t check the project type accordingly
    • tfa improvements
  • npm 1.0.1:
    • the npm step has been extended with an input where you can provide a preferred npm version to use. The supplied version will be installed before running your npm command.
    • previously, we used the system preinstalled version. With this new release, we first check user provided version, then check the package.json and only after then we fall back to the system installed version. If no npm is found, we install the latest available version from the operating systems package manager.
    • the step has been migrated onto the Go toolkit from plain shell
    • recently reported 1.0.0 regressions have been fixed.
    • current release supports standard semantic version strings in the form ‘X.Y.Z’ only, that is, version strings containing caret or tilde and version ranges will not work.
    • however, from this patch release, the step will fall back to use the system preinstalled npm in case it fails to read a proper npm version
  • open-vpn 0.0.2:
  • openstf-connect 0.0.7:
    • increase HTTP timeout to 30s
    • improve log formatting
  • openstf-disconnect 0.0.5:
    • add ADB disconnect to release process
  • project-scanner 1.6.8:
    • the dependencies updated to the latest version
    • the step received a fresh dependency update
  • sign-apk 1.2.4:
    • fix the bug, which overrode the exported signed build artifact’s ( $BITRISE_SIGNED_APK_PATH ) extension to .apk even if it was a .abb
  • virtual-device-testing-for-android 1.0.5:
    • update device model list. New devices: Pixel 2, Nexus 7 16_9 aspect ratio (beta)
  • xcode-archive 2.4.17:
    • scheme is not found issue fix: the xcode-proj core package thought that productType is a required property for every target type, this missing property led to a shallowed error
  • xcode-build-for-test 0.2.1:
    • fixed a bug related to the xctestrun file path. The step now correctly assumes that the path is generated based on the scheme name, not the project name. related error message: no xctestrun file found with pattern: [...]*.xctestrun
  • xcode-test 2.0.0:
    • we removed the wait_for_simulator_boot input from the step and introduced the headless_mode input instead.
    • with headless mode enabled the step will not force the simulator to boot in the foreground. Instead, xcodebuild will run the tests in the background.

This topic was automatically closed after 90 days. New replies are no longer allowed.