Update Fishhook Podspec to refer to the latest API-Changing Commit instead of Release 0.1. #22
Conversation
…stead of the older release version
|
@grp, just checking if you had any updates on this Pull Request. |
|
Hi, I'd prefer to keep this as is for now. In general I suggest tracking master rather than a specific release commit. |
|
Considering that master has been updated, I'd suggest you should update the Podspec and releases as well. Now we have an older version of fishhook being obtained by CocoaPods than by cloning from Github. |
|
@grp, we use fishhook for our internal project that is being used by multiple teams. It is highly cumbersome to have all their Podfiles point to head. Would you prefer it if we changed the Podspec to point to master instead of the commit here? We would really appreciate any help you could provide us here. |
|
Hey, sorry about that. I'll see if I can do a normal CocoaPods release today. |
|
That would be great! Thank you very much. |
|
Hey @grp, just checking if you had an ETA for the update by any chance. |
|
Sorry about that (again) — I just pushed 0.2 to master and to CocoaPods trunk. |
|
Thanks a ton for the update @grp, really appreciate it. |
Related Issue : #20
When the pull request - #18 was merged, it broke the API for anyone using fishhook with CocoaPods since the repo at HEAD has a different interface from the Pods Sources.
In the Podspec, we are currently using the release version of fishhook. However, creating releases can be extremely tedious, especially with the case of a single maintainer and it would be much better if we could simply point to a specific commit.