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

bitrise-tools
cli
announcements
#1

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

We ship a new bitrise cli version every month. The new release will be available on the bitrise.io virtual 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.37.0)

1. Tools update

  • envman version bumped to 2.2.10
  • stepman version bumped to 0.11.12

2. Default plugins update

  • workflow-editor plugin version bumped to 1.1.67

3. Go dependencies update


New steps

  • appcenter-deploy-android 1.0.0
  • appcenter-deploy-ios 1.0.0
  • create-apple-documentation 1.0.0
  • msbuild-sonarscanner-end 0.9.0

Step updates

  • activate-ssh-key 4.0.5:
    • step input updated
  • appcenter-app-release 1.0.5:
  • avd-manager 1.0.1:
    • fixed issue: Failed to run phase, error: fork/exec /Users/vagrant/Library/Developer/Xamarin/android-sdk-macosx/emulator/emulator-headless: no such file or directory.
      Background: The binary emulator-headless is now retired. Headless builds of the engine are now launched via emulator -no-window, thus unifying the previously separate (but similar) paths (https://androidstudio.googleblog.com/2019/12/emulator-29211-and-amd-hypervisor-12-to.html).
      Thanks for @dweekly for the contribution! :1st_place_medal:
    • fixed emulator creation process
  • cache-pull 2.1.3:
    • caches created on a different stack will be invalidated to preserve correctness. Updated the source of stack ID used for this purpose
    • step description update
  • cache-push 2.2.3:
    • caches created on a different stack will be invalidated to preserve correctness. Updated the source of stack ID used for this purpose
  • certificate-and-profile-installer 1.10.2:
    • updated step description
  • deploy-to-bitrise-io 1.9.4:
    • fixed: failed test reports are not marked as failed when test class is inherited or embedded
  • expo-detach 0.10.1:
    • updated step.yml to match sharing requirements
  • firebase-app-distribution 0.5.0:
    • uses another method to install Firebase CLI which is compatible with Macs
  • flutter-analyze 0.1.2:
    • fixed: issue with regards to flutter analyze failing with exit 1 for info level warnings, contributor: @doc-rj-celltrak :1st_place_medal:
  • google-play-deploy 3.0.1:
    • updated Google Play Developer API to version v3. Earlier API versions will be deprecated on December 1, 2019 (https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html).
    • removed APK file path (apk_path) input after a deprecation period, please use 'App file path` (app_path) instead.
    • removed Untrack blocking versions? (untrack_blocking_versions) input. Other than the current target track releases are not changed, as it is not needed with the current API
    • accept release notes for more languages added in the Directory of localized what's new files (whatsnews_dir) input. Locales with a single language subtag like ca are now accepted
  • hockeyapp-deploy 2.4.4:
  • hockeyapp-deploy-android 1.3.3:
  • ios-auto-provision 1.4.2:
    • redacting certificate password in the logs, if debug log is enabled or certificate import fails
  • msbuild-sonarscanner-begin 0.9.2:
  • nunit-runner 1.4.1:
    • fixed: log order when the test fails.
    • language correction
  • saucelabs-espresso-app-automate 0.1.4:
  • tryoutapps-shaman 1.0.4:
  • xamarin-archive 1.5.2:
  • xcode-archive 2.7.1:
    • this release fixes an issue when there are framework dSYMs found, but not app dSYM. The symptom is, that the exported dSYMs zip archive includes the current working directory contents.
    • the issue arises when the main target has DEBUG_INFORMATION_FORMAT build setting set to DWARF (instead of DWARF with dSYM), while the included frameworks, pods, etc… have DWARF with dSYM set.
  • xcode-test 2.4.3:
    • fixed handling of specific version (e.g. 13.2) in OS version (simulator_os_version) input. This issue was a regression introduced in version 2.4.2. An example error message received in this case was: failed to get simulator udid, error: %!(EXTRA *errors.errorString=no simulators found for os version: 13.2)
  • xctest-html-report 0.2.1:
    • Changes*
      • update the expected path list of the generated index.html
      • update the test workflows to test the provided test results in subfolders as well
  • xcuitestbrowserstack 1.0.8:
0 Likes