Open kelson42 opened 2 months ago
It seems to me that we are re-using the tags that were used to created the TestFlight releases (and which was approved by Apple), and we do not create a new tag. In other words we do want to re-create the very same macOS build for FTP, as part of the GitHub release process, so we pointing it to the (Apple approved) TestFlight tag. (In case of a TestFlight build, the trigger is the appropriate tag. In case of the release, the trigger is the release itself.)
To me the workflow should be as such:
testflight
when you want to do Testflight release. If this tag already exists, then removes/superseeds older version.x.y.z
and release in GitHub.I've updated the readme and the CD workflow to reflect the above requirements.
For some reason it is
testflight-3.5.2
and it should be3.5.2
Unclear - at least right now - to me why we don't have a proper tag.