jpsim/[email protected] #374
Conversation
![publish-to-bcr-bot[bot]](https://avatars.githubusercontent.com/in/234555?s=60&v=4){kind=small}
|
@fmeum sorry to bug you on this but could you please try running CI again? |
|
@jpsim Happy to do so. CI is still failing, but with a different error. |
|
@fmeum I suspect it may be because SourceKitten requires Swift 5.7 to compile as of the latest release. Does bazel-central-registry's CI machines have Xcode 14.x installed? |
|
i guess in the meantime we can disable the macOS CI but leave the linux stuff since it's downloading the required version |
|
@meteorcloudy Do you think it would be possible to update the macOS/Xcode version used by the runners? The Swift modules all seem to depend on more recent features. |
|
Yes, we need to upgrade macOS and Xcode version for CI Mac VMs, currently this is manual work. Related issues: bazelbuild/continuous-integration#1348 bazelbuild/continuous-integration#1431 /cc @fweikert We'll look into this shortly! |
Which currently doesn't require Xcode 14, despite having officially dropped support for Xcode 13.
|
In the meantime, I've pushed another change that might unblock this from landing before Xcode is updated on CI. Could someone please kick off a new CI run? |
Release author: @jpsim.
Automated by Publish to BCR.