Assuming the iOS build has been tested e.g. on Dan's local Mac or on a Parallels VM for macOS (as a clean build machine, see e.g. kb article)
--> i.e. avoiding running GitHub Runners with macOS with the 10x penalty multiplier compared to Linux runners.
Continuous Integration operates on the entire Repo anyway, and before PR mergers into main, comprehensive tests, including iOS, are run on dev's Macs anyway i.e. no dedicated 'CI' for iOS is needed right now, only Deployment Automation.
[ ] Automate uploading to App Store Connect etc. via Apple API
Refer also to #16
Depends on #17
Assuming the iOS build has been tested e.g. on Dan's local Mac or on a Parallels VM for macOS (as a clean build machine, see e.g. kb article) --> i.e. avoiding running GitHub Runners with macOS with the 10x penalty multiplier compared to Linux runners.
Continuous Integration operates on the entire Repo anyway, and before PR mergers into main, comprehensive tests, including iOS, are run on dev's Macs anyway i.e. no dedicated 'CI' for iOS is needed right now, only Deployment Automation.