Swift package manager support..

Question

Swift package manager support..

lvnkmn opened this issue 5 years ago · 12 comments

lvnkmn commented 5 years ago

..would be great!

Answer 1 · 2019-09-18T16:01:19.000Z

And I've implemented this in my fork, I will create a pull request shortly.

Answer 2 · 2019-12-13T16:20:35.000Z

Super nice that this is merged. Looking forward to a release of this.

Answer 3 · 2020-01-09T14:35:05.000Z

@chiahsien, can you create a release using this code? Until then SPM cannot be used with version numbers.

Answer 4 · 2020-01-12T23:56:10.000Z

@lvnkmn Please send me the PR. I don’t do iOS for a while and i need support from community. 😃

Answer 5 · 2020-01-13T00:42:30.000Z

@chiahsien I think only you as the project owner (or another collaborator who has the permission) can do this. You have created releases on GitHub before (like this one). But just in case, this shows how you can create a new release

Answer 6 · 2020-01-13T11:51:15.000Z

@ApolloZhu is right.

To release a version for SPM, all you have to do is (considering the development branch is stable and contains everything that needs to be released). ->

Merge development into master
Tag it with 0.10.0 considering there's no breaking changes or 1.0.0 when there's been breaking changes since last release.
Make sure you push the changes and tags.

To also make that release available to cocoapods, you'd have to also update the podspec with the new version and upload to their specs repo like explained here (Submitting Open Source Code).

Answer 7 · 2020-01-13T15:17:45.000Z

I understand. But since this project is in maintenance mode, I think it'd be better to follow latest master branch instead of certain tag.

I'm happy to merge PR into master, but I'm lazy to release a new tag and update CocoaPods/SPM, and sometimes it doesn't worth it to release a new tag for a minor patch.

How do you think? Any suggestions?

Answer 8 · 2020-01-13T16:43:19.000Z

Ok. What I could do, is cherry pick the SPM commit and create a PR which you can merge into master.

In order to get some benefit out of this, is to tag this with a += 0.0.1 version so the new version would be 0.9.8

Eventhough for github this would count as a release, there would be no added benefit of creating a cocoapods release for it, so you can skip that for this one. SPM users would be happy though. Every release after that would just work for SPM with no added work.

Sounds reasonable?

Answer 9 · 2020-01-13T16:46:32.000Z

Or you could do the cherry pick into master + tag of course 🙂

Answer 10 · 2020-01-15T15:38:15.000Z

I’ve pushed a new tag, please help to check if it works.

Answer 11 · 2020-01-15T18:38:32.000Z

Thanks. Will let you know. First thing tomorrow morning.

Answer 12 · 2020-01-16T10:33:41.000Z

It works for me. So far no issues. Will close this. Thanks for the work!