Upload a new release built with Swift 2.2 for Carthage
chrismanderson opened this issue · 10 comments
Getting the Module file was created by an older version of the compiler error when building PermissionScope via Carthage.
Seems to be a similar issue to #110.
I was still able to build with the --no-use-binaries flag in Carthage.
Yeah, the archive uploaded was built using swift 2.1 and there's a note in the readme about it.
Thanks @chrismanderson, please use --no-use-binaries for now and we'll upload a new binary (or not! this process is getting frustrating) with the next release.
Travis CI can automatically upload assets to your git tags on your GitHub repository.
Carthage auto-archive ?
Edit: More info here facebookarchive/ios-snapshot-test-case#81 and Use travis-ci to upload your tagged prebuild frameworks
Keeping up with Xcode releases is frustrating? That's totally the first time anyone has ever said that. 😀
Thanks for that information, appreciate it.
@chrismanderson No, just reuploading new binaries for Carthage when nothing has changed. Makes me rethink the benefits from having uploaded binaries in the first place.
@bre7 We'd then be dependent on Travis to support new Xcode releases. I wonder if we can just rebuild with Xcode 7.3 and add to the old release?
Yes, you can add a new archive to an old release
OK, will give that a shot later today.
Thanks for uploading this @bre7! It's weird that I can't find a record of a changed release binary anywhere in github, right?
True, there's no "uploaded date" in the release panel though it's part of the api https://api.github.com/repos/nickoneill/PermissionScope/releases/2512203.
BTW, it's easier to use this tool to upload files to releases: https://github.com/aktau/github-release