6.0.0: Retry flaky tests by default

The default value of test_repetition_mode is now retry_on_failure. This means that failed tests are retried at most maximum_test_repetitions times (default: 3) before considering the test as failed.

What's Changed

• Update module golang.org/x/crypto to v0.17.0 [SECURITY] by @renovate in #243
• Remove pre-Xcode-13 code by @ofalvai in #251
• Upgrade go-xcode, handle breaking changes by @ofalvai in #252
• Retry flaky tests by default by @ofalvai in #253

Full Changelog: 5.1.1...6.0.0

5.1.1

What's Changed

• Fixed error logging when export fails.

5.1.0

What's Changed

• Update system report link by @ofalvai in #238
• Add visionOS support by @ofalvai in #241

Full Changelog: 5.0.1...5.1.0

5.0.1

What's Changed

• Improve destination error messages by @ofalvai in #236

Full Changelog: 5.0.0...5.0.1

5.0.0

What's Changed

By default the xcbeautify log_formatter is used. The previous default xcpretty is still available.

The Device destination specifier (destination) Input now uses the device called Bitrise iOS default by default.
Where already created, this device is:

• iPhone 8 with iOS Simulator runtime 16 and earlier (Xcode 14 and earlier)
• iPhone 11 with iOS Simulator runtime 17.0 and later (shipped in Xcode 15 beta)
  If a device with this name is not found (e.g. in a local dev environment), the first matching (platform and OS specifiers are considered) device will be selected.

The Enable collecting cache content (cache_level) Input is set to none by default. The previous swift_packages is still available.
This option is needed with branch-based (legacy) caching.
With the newer, better performing key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages. See devcenter for more information.

Full Changelog: 4.7.5...5.0.0

4.7.5

What's Changed

Fixed fallback to xcodebuild when xcpretty/xcbeautify log formatter is unavailable.

Before:

Checking log formatter (xcbeautify) version
Failed to install Step dependencies:
  installing log formatter failed:
    failed to run xcbeautify command:
      executing command failed (xcbeautify "--version"):
        exec: "xcbeautify":
          executable file not found in $PATH
Switching to xcodebuild for output tool
Running the tests...
[16:58:43] $ set -o pipefail && xcodebuild "-workspace"[ ... ] | xcbeautify
xcbeautify command failed: executing command failed (xcbeautify): exec: not started
Exit code:  -1

After:

Checking log formatter (xcbeautify) version
Checking log formatter failed: failed to run xcbeautify command: executing command failed (xcbeautify "--version"): exec: "xcbeautify": executable file not found in $PATH
Switching back to xcodebuild log formatter.

Running the tests...
[16:57:02] $ xcodebuild "-workspace" [...]

Full Changelog: 4.7.4...4.7.5

4.7.4

What's Changed

Check for iOS Simulator <-> Xcode compatibility when using latest device for destination.

When Xcode 14.3 and Xcode 15 (beta) is present on the same machine, requiring the latest (this is the default) version of the Simulator runtime, will find iOS 17 (beta). This is undesirable as the beta Simulator can be unstable or at least not officially supported by earlier Xcodes.

In practice Xcode still works with newer runtimes, at least across the same major version (despite this table: https://developer.apple.com/support/xcode/). When there are different major versions, there is some risk of not working right.

Full Changelog: 4.7.3...4.7.4

4.7.3

What's Changed

If arch key is present in the xcodebuild -destination flag, pass it through. This allows selecting a Rosetta compatible Simulator runtime (13.7 or 14.5).

Reported in: #226

4.7.2

What's Changed

• Update iOS simulator default input, fix device lookup by @lpusok in #227
• Revert default device by @ofalvai in #228

Full Changelog: 4.7.1...4.7.2

4.7.1

What's Changed

• Update module golang.org/x/text to v0.3.8 [SECURITY] by @renovate in #222

Full Changelog: 4.7.0...4.7.1