Maybe the root cause is because we're using macos-latest, and they deployed a new version to that, silently breaking our workflow.

Maybe it's a different issue with a minor/patch version of either fwal/setup-swift@v1 or ruby/setup-ruby@v1. Not sure.

This needs to be investigated