Thanks for the suggestion. That works in our case well enough to unblock us, although it unfortunately adds ~3-4 minutes of homebrew installation to a number of our build steps, which seems pretty wasteful. @maxcan have you heard anything from Apple to make you think it is not a bug, but a deliberate choice?

I don't know if this is your issue, but be aware that for instance running "Test" as part of your workflow means that Xcode Cloud will first run a build-for-testing action, and then a number of test-without-building actions. Each of those will run in a seperate environment, so you will need to install the tools you need in both actions. You can check against $CI_XCODEBUILD_ACTION in your scripts.