Changelog of Bitrise
We ship a new bitrise cli version on the second Tuesday of 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.29.0)
1. Fixed a small issue with the previously introduced test deploy directory export
2. Default plugins now installed from bitrise-io
organization. (instead of bitrise-core
)
3. Tools update
4. Default plugins update
workflow-editor
plugin version bumped to 1.1.52init
plugin version bumped to 1.1.1analytics
plugin version bumped to 0.10.1step
plugin version bumped to 0.9.9
5. Go dependencies update
New version of Stepman (0.11.3)
- Go dependencies update
New version of Envman (2.2.2)
- Go dependencies update
New steps
- swift-package-manager-build-for-mac 0.0.1
- swift-package-manager-test-for-mac 0.0.1
- swift-package-manager-xcodeproj-for-mac 0.0.1
Step updates
- android-build 0.9.6:
- added
--console=plain
to the tasks list command
- added
- android-build-for-ui-testing 0.1.1:
- added
--console=plain
to the tasks list command
- added
- android-lint 0.9.6:
- added
--console=plain
to the tasks list command
- added
- android-unit-test 0.9.6:
- added
--console=plain
to the tasks list command
- added
- cache-push 2.1.1:
- fix for the issue which led to constantly growing cache archive files.
- the ignore and skip exclude patterns were interleaved incorrectly in case of include path with file change indicator, that’s why the step added files to the cache archive which should not be added.
- major step revision has done for easier maintenance, new unit and integration tests introduced to ensure the correct behavior
- the issue fixed when the logic did not skipped file reading for non generic files types
- deploy-to-itunesconnect-deliver 2.15.0:
- Two-Factor Authentication:*
- the step now supports two-factor authentication.
- it will use the Bitrise.io built-in Apple Dev Portal auth feature to connect your Apple Dev Portal account even if the two-factor authentication is enabled for your Apple developer account.
- how to connect your developer account to Bitrise.io:
- https://devcenter.bitrise.io/getting-started/signing-up/connecting-apple-dev-account
- Note:*
- “2FA will be required to sign in to your Apple Developer account and certificates, identifiers and profiles starting February 27” - Apple Adds Two-Factor Authentication Requirement for Developer Accounts | Technology News
- fastlane 2.4.0:
- step repository revision, dependency and step definition update
- If you want to use two-factor authentication for Fastlane on Bitrise.io use this step.*
- Two-Factor Authentication:*
- the step now supports two-factor authentication.
- it will use the Bitrise.io built-in Apple Dev Portal auth feature to connect your Apple Dev Portal account even if the two-factor authentication is enabled for your Apple developer account.
- how to connect your developer account to Bitrise.io:
- https://devcenter.bitrise.io/getting-started/signing-up/connecting-apple-dev-account
- Note:*
- “2FA will be required to sign in to your Apple Developer account and certificates, identifiers and profiles starting February 27” - Apple Adds Two-Factor Authentication Requirement for Developer Accounts | Technology News
- generate-text-file 0.1.0:
- this release is a rewrite in Go. In addition, it also transfers the step to the
bitrise-community
organisation as it was abandoned by its original author
- this release is a rewrite in Go. In addition, it also transfers the step to the
- generic-file-storage 0.9.1:
- add an ignore list of keys. The step will not try to download the env provided file if the env’s key is in the ignore list
- npm 1.0.2:
- fixed swallowed error logs: there was a regression which caused the full output of the specified npm command – including any error logs – to be hidden. In case of an error, the user seen the exit code only
- xcode-test 2.2.0:
- Export .xcresult’s path at the end of the step*
- since 2.1.0 the step uses the -resultBundlePath flag for the xcodebuild command which will replace the result files to the provided path.
- this fix will export the
BITRISE_XCRESULT_PATH
env which points to the generated.xcresult
package
- xcode-test-mac 1.3.0:
- added support for providing optional additional options to xcodebuild via xcodebuild_options, similar to the existing Xcode Archive step for iOS. (Add support for xcodebuild additional options by sebj · Pull Request #12 · bitrise-steplib/steps-xcode-test-mac · GitHub) - Thanks to @sebj
- fix the key and value order in
validateRequiredInput
. (Pass key and value in correct order to `validateRequiredInput` by kitasuke · Pull Request #11 · bitrise-steplib/steps-xcode-test-mac · GitHub) - Thanks to @kitasuke - maintenance (Maintenance by BirmacherAkos · Pull Request #13 · bitrise-steplib/steps-xcode-test-mac · GitHub):
-
- update the go-test, golint, errchek etc…
-
- update the yml for the new release flow
- New input:*
xcodebuild_options
- options added to the end of the xcodebuild call. You can use multiple options, separated by a space character.\
- example:
-xcconfig PATH -verbose