Several downstream projects are broken due to two different Bazel changes that are incompatible with older versions of rules_apple:

target 'StdRedirect.dylib' not declared in package 'tools/objc' caused by 67586a2 (June 8th).
Impacted projects:

• Bazel Examples: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2124#12f494ce-91ec-484b-b95d-de1d8ce7630f
• Tulsi: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2129#4af84457-5ca9-4fe5-b3db-fe9d5b1201e1 (Tulsi is broken with Bazel@HEAD tulsi#258)

'apple_common' value has no field or method 'objc_proto_aspect' caused by d683067 (May 3rd).
Impacted projects:

• TensorFlow: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2124#4354d0da-1f54-4389-81cf-d1ccce0b6bea
• FlatBuffers: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2129#1a2475cc-c60f-4ecd-aa4c-764a7386bbb0

rules_apple itself passes all tests with Bazel-at-HEAD, which means that the aforementioned projects should update their version of rules_apple. Unfortunately this isn't trivial since they are stuck at older Bazel versions (3.7.*).