I was also surprised to see protobuf take a dep on rules_apple. I could only find one use in this repo for it. It sort of complicates how protobuf is used in rules_swift as it depends on protobuf which depends on rules_apple which itself depends on rules_swift

cc @jguamie

This PR is failing most of our windows platform tests. It looks like the absence of swiftc.exe was treated as a failure until rules_swift 3.0, when this commit landed, fixing bazelbuild/rules_swift#1483. The error message we see in the failures (No 'swiftc.exe' executable found in Path) doesn't exist in rules_swift any more, further hinting that the version of rules_swift being pulled in is out of date - maybe as old as 2.4.0, which is the current default.

Can you try including a bump to the version of rules_swift so that rules_apple pulls in a version with the fix?

@JasonLunn Hmm interesting. protobuf doesn't have a direct dep on rules_swift and I'm not sure it can? rules_swift has a dependency on protobuf. The version 2.x is being brought in by rules_apple transitively

Pushed a change that uses an override to see if that helps

Updated! I think we'll likely want to follow this up by providing a apple_binary rule in apple_support so we can drop the rules_apple dependency in this repo.

Not sure whats up with the other failing tests but they dont seem related to Bazel

I see yall opened #25534, ill close this in favor of that one. I forgot circular deps are fine in bzlmod so i think were good here with the changes in that PR

No need to close this manually, automation will close this when a fix lands.